fix(sync): add explicit --base and --repo to gh pr create - #22
Merged
Merged
Conversation
The gh pr create command in a shallow clone (--depth=1) fails with "Head sha can't be blank, Base sha can't be blank" because it cannot infer the base branch from the truncated git history. Adding --base main and --repo explicitly resolves the ambiguity. https://claude.ai/code/session_01FC8XoyssN5v6hQCTtcjoB5
Owner
Author
|
|
iamkayleb
temporarily deployed
to
agent-high-privilege
March 25, 2026 10:44 — with 
GitHub Actions
Inactive
Owner
Author
Automated Status SummaryHead SHA: dc92810
Coverage Overview
Coverage Trend
Top Coverage Hotspots (lowest coverage)
Updated automatically; will refresh on subsequent CI/Docker completions. Keepalive checklistScopeNo scope information available Tasks
Acceptance criteria
|
iamkayleb
pushed a commit
that referenced
this pull request
Aug 22, 2026
…ke#2956) * feat(fleet): issue-format guard synced to every consumer repo Every automated lane reaches an issue through a LABEL. An issue filed with no label and no Tasks/Acceptance block is therefore invisible to the whole pipeline: nothing validates it, nothing optimises it, nothing claims it. Local automation that files *findings* rather than *work orders* produces exactly that — good evidence, permanently unactionable. Observed in Fine-Art-Archive stranske#406-409: four well-evidenced audit findings from a local audit script, zero labels between them, no Tasks section. That repo already had agents-issue-optimizer.yml with a `format` phase — but it triggers on `issues: [labeled]`, so an unlabelled issue never reached the very machinery built to fix it. Adds, and registers in .github/sync-manifest.yml so all 13 consumer repos receive them: * .github/scripts/issue_format.py — the single fleet definition of "agent-processable", mirroring docs/AGENT_ISSUE_FORMAT.md rather than inventing a parallel standard: Tasks and Acceptance Criteria required; Why/Scope/Non-Goals recommended; at least one acceptance criterion must name a real test, runnable command or observable verification gate. Also flags Tasks without checkboxes and the guide's banned subjective adjectives. Pure stdlib on purpose so it runs on a bare runner with no install step, and so local filers can pre-flight with `python .github/scripts/issue_format.py <body>` before `gh issue create` (non-zero exit = unfit). * templates/consumer-repo/.github/workflows/agents-issue-format-guard.yml — validates on opened/edited/reopened and, on failure, applies `agents:format`, the label the optimizer already listens for. So a bad issue is ROUTED to the repairer rather than merely flagged; the label is cleared once the body conforms. Skips `agents:formatted` so it never fights the optimizer's own edits, fingerprints its comment by body hash so an edit burst cannot spam a thread, skips cleanly if the validator has not synced yet, and tolerates a repo whose label set predates `agents:format`. Verified: manifest compiles (219 copy entries), validate_template_completeness passes --strict, actions/checkout SHA-pinned to match the template convention, and the validator rejects all four real stranske#406-409 bodies while accepting a conforming one. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(fleet): exempt tracking-only issues from the format guard Running the guard across a real repo's whole open-issue list surfaced the gap: 6 of 10 issues legitimately are NOT work orders and never will be — - #21/#22/#23 blocked epics whose bodies say 'do not dispatch' - #36/stranske#114 self-described tracking issues - #80 Renovate's Dependency Dashboard Nagging those forever trains people to ignore the guard, which costs more than it catches. So the guard now skips an issue when any of: * label tracker:durable or wontfix * a bot author (Renovate, Dependabot, any *[bot]*) * a body declaring 'do not dispatch' / 'not a repo|cloud coding task' Requires author in the gh issue view field set. All downstream steps honour the exemption, so an exempt issue is neither commented on nor labelled. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * chore(autofix): formatting/lint * fix: restore issue format guard source and routing * fix: regenerate renovate ownership for issue-format guard paths CI failed because sync-manifest added issue_format.py and agents-issue-format-guard.yml without refreshing the generated consumer-managed-paths preset. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Codex Automation <codex-automation@users.noreply.github.com> Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The gh pr create command in a shallow clone (--depth=1) fails with "Head sha can't be blank, Base sha can't be blank" because it cannot infer the base branch from the truncated git history.
Adding --base main and --repo explicitly resolves the ambiguity.
https://claude.ai/code/session_01FC8XoyssN5v6hQCTtcjoB5