* fix(ship): make the five judge-flagged workflow spots match the code (GST-1346)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* fix(ship): carry runs the pregate before its push (review fix)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* fix(ship): carry pushes early, waits for CI, then pregates; restore stage 1 wording (fix-check)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* docs: diff-plus-blocking stops at the third fix cycle; carry order matches ship Step 1 (Step 14.5)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* chore: changelog and TODOS
Documentation: updated
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
* Revert "docs: diff-plus-blocking stops at the third fix cycle; carry order matches ship Step 1 (Step 14.5)"
This reverts commit 5151144c04.
---------
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
3.4 KiB
Step 6.5: Early Greptile PR (after the free tests pass)
When the repo uses Greptile (and greptile is in a review-bot list), push and open the PR
now so Greptile reviews while Steps 7–9 run; Step 10 collects its comments.
~/.claude/skills/gstack/bin/gstack-greptile-early detect
-
GREPTILE_EARLY: off— print the reason (and any turn-back-on line) and continue to Step 7. -
GREPTILE_EARLY: ask(a public repo, or unknown visibility, the first time) — AskUserQuestion:This repo is public. Early Greptile review pushes this branch and opens a draft PR before /ship's own review, so the code is visible before that review finishes. If /ship stops later, the draft stays up with a comment saying why.
A) Push early for this repo (remembered) · B) Keep today's order for this repo (remembered). Run
~/.claude/skills/gstack/bin/gstack-greptile-early consent yes(A) orconsent no(B). B continues to Step 7. Neither answer undoes Step 5's consent-free CI-carry push and draft PR. -
GREPTILE_EARLY: on, or after A — show the user the printedGreptile: found …line, then follow 1-3.
1. Push: git push -u origin <branch-name>. If it fails, record
"Greptile early review: not run (push failed)" and continue to Step 7; Step 17 pushes later.
2. Write a provisional <type>: <summary> title (Step 18 replaces it) into a private file:
_GT="$(git rev-parse --show-toplevel 2>/dev/null || pwd)/.gstack/tmp"
mkdir -p "$_GT" && chmod 700 "$_GT" || { echo "Not sent: cannot create $_GT for the text file." >&2; exit 1; }
_EX=$(git rev-parse --git-path info/exclude 2>/dev/null) && mkdir -p "$(dirname "$_EX")" && { grep -qxF '/.gstack/tmp/' "$_EX" 2>/dev/null || echo '/.gstack/tmp/' >> "$_EX"; }
TITLE_FILE=$(mktemp "${_GT:?}/early-title.XXXXXX") || { echo "Not sent: mktemp failed in $_GT." >&2; exit 1; }; echo "TITLE_FILE: $TITLE_FILE (name: ${TITLE_FILE##*/})"
Write the text into each printed file with your file-write tool (Claude Code's Write tool needs a Read of the empty file first), exactly as it should appear. The text never goes into a shell command, heredoc or quoted argument. If a write fails or is refused, do not send: print the cause, the file path and the command below for sending by hand.
3. Open the draft with the printed name. Add --ready only when the user asked
for a non-draft PR:
TITLE_FILE="$(git rev-parse --show-toplevel 2>/dev/null || pwd)/.gstack/tmp/<title-file-name>"
~/.claude/skills/gstack/bin/gstack-greptile-early open --base <base> --title-file "$TITLE_FILE"
It opens the PR through gstack-post (body: /ship opened it early) and
posts one @greptileai comment when Greptile skips drafts. Save the printed
EARLY_PR and EARLY_PR_OPENED_AT in the invocation record. EARLY_PR: none means a
PR was already open (Step 5's draft too): Step 10 triages it. Exit 1 or 2 means gstack-post
flagged the provisional title: write a plainer one and rerun. Exit 3: record the error
and continue without early review.
If /ship stops after the early PR opened and before Step 19 publishes, leave the
draft open (never close or force-push it) and post one comment saying /ship stopped
and why: write the reason into a private file, then run
~/.claude/skills/gstack/bin/gstack-post pr-comment <pr-number> --body-file <that file>.