WEBVTT

1
00:00:00.000 --> 00:00:04.000
Skylos Cloud · Chapter 21: Pull requests board
See whose turn every pull request is, and approve risky changes with a tick.

2
00:00:04.000 --> 00:00:11.000
Step 1: Every pull request has one owner right now
Skylos sorts each pull request by who has to act next: the author, a team, or nobody.

3
00:00:11.000 --> 00:00:18.000
Step 2: An AI agent touched payment code
Claude wrote pull request #12 and it changes the protected Payments path, so the Skylos check waits for the Leads team.

4
00:00:18.000 --> 00:00:25.500
Step 3: One board for every pull request
Pull requests, then Board. Each column says whose turn it is. List and Board show the same pull requests.

5
00:00:25.500 --> 00:00:31.000
Step 4: Only what's waiting on you
Waiting on you keeps the cards you can act on: approvals your team owns, and fixes on your own pull requests.

6
00:00:31.000 --> 00:00:38.000
Step 5: Open a card
The panel says why the pull request is here and lists each thing that needs your approval.

7
00:00:38.000 --> 00:00:45.000
Step 6: Tick it, add a note, approve
The note is required and goes in the audit log. You can only approve paths your team owns, and never your own change.

8
00:00:45.000 --> 00:00:50.500
Step 7: Approved, and recorded
Skylos saves who approved what, for which commit, and re-runs the GitHub check.

9
00:00:50.500 --> 00:00:56.000
Step 8: The card moves by itself
Nothing else blocks #12, so it moves to Ready to merge.

10
00:00:56.000 --> 00:01:01.500
Step 9: GitHub turns green
The Skylos check now passes on GitHub. The merge button is the team's normal one.

11
00:01:01.500 --> 00:01:08.500
Step 10: Or send it back
For #13, write what needs to change and choose Request changes instead.

12
00:01:08.500 --> 00:01:16.000
Step 11: It's the author's turn again
#13 moves to Needs fixes with your note on it. When the author pushes a fix, Skylos checks the new commit.

13
00:01:16.000 --> 00:01:21.500
Step 12: The author sees it on GitHub too
Skylos posts your note as a comment on the pull request, so the author doesn't need to open Skylos.

14
00:01:21.500 --> 00:01:28.500
Recap: One board: whose turn each pull request is · Waiting on you: only what you can act on · Tick what you approve; the note goes in the audit log · Approving re-runs the GitHub check · Request changes posts your note on GitHub
Next: Chapter 22 · Compliance reports
