| 70 | 70 | | 7. **Watch the checks.** `g1t pr checks --watch --fail-fast`. When one |
| 71 | 71 | | fails, `g1t run logs --failed` says why; fix it and push again. |
| 72 | 72 | | 8. **Finish.** When the definition of done is met and the checks pass, |
| 73 | | − | `g1t pr ready --summary "what changed and why"`, then `g1t pr merge` |
| 74 | | − | when you are allowed to merge. With the merge queue on, merging adds the |
| 73 | + | `g1t pr ready --summary "what changed and why"` (add a screenshot with |
| 74 | + | `--attach shot.png`, or upload one with `g1t attach FILE` and paste the |
| 75 | + | Markdown it prints; never commit an image just to link it), then |
| 76 | + | `g1t pr merge` when you are allowed to merge. With the merge queue on, merging adds the |
| 75 | 77 | | pull request to the queue; if the queue reports an integration failure, |
| 76 | 78 | | use the `fix-integration` skill. The merge closes the issue the pull |
| 77 | 79 | | request was made for. Where you commit straight to the default branch |