You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Fail template sync when its source pull fails #887
A failed source pull can leave Template Sync green and without a proposal. A maintainer then sees a successful run even though the consumer never received the template changes.
Evidence
The pinned upstream action catches the nonzero pull, writes warnings and returns the status of target sign-in. Its inputs do not expose a fail-on-pull option. The original tag-collision case in #861 reached that path. The released no-tag parameters fix that cause, as confirmed by a real KHoist sync, while other failed pulls can still reach the same path.
Acceptance
A fetch, authentication or merge failure reaches a failed native workflow verdict and does not produce a misleading no-change receipt.
A genuinely up-to-date consumer can still report success without a proposal. A normal change still creates a valid signed proposal and preserves caller-owned files and tags.
Exercise the real execution boundary with unavailable source, conflicting merge and up-to-date controls. Preserve the reviewed authentication, signing and caller scopes.
Prefer an upstream supported outcome if available. Otherwise make the smallest catalogue-owned change with current-head CI and review, then verify a normal consumer run.
Follow-up to #861. The tag-collision repair and its consumer adoption are already delivered. This work does not require the KHoist caller to change its released tag protection.
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
🤖 Generated by the Agentic Engineer (interactive Claude Code session)
Done. The fix from #891 is released (v20.1.20, also in v21.0.0), and the last open point, a normal consumer run, is now verified on devantler-tech/ascoachingogvaner, which I moved to v21.0.0 in devantler-tech/ascoachingogvaner#366.
One thing surfaced on the way: the first attempt of the first run was marked failed by the signing step's branch readback, although the proposal and its signature were correct. That is a separate defect, tracked in #897, with a fix prepared.
Activity
coderabbitai commentedon Nov 9, 2026
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
chore: agent-claim #887 nonce=a2864913933d062aa1e6ecde52f7261c
docs(template-sync): correct how an up-to-date consumer passes the pu…
test(template-sync): cover a consumer that already holds the template…
fix(template-sync): fail the run when the template pull fails (#891)
devantler commentedon Nov 11, 2026
Done. The fix from #891 is released (v20.1.20, also in v21.0.0), and the last open point, a normal consumer run, is now verified on
devantler-tech/ascoachingogvaner, which I moved to v21.0.0 in devantler-tech/ascoachingogvaner#366.test-template-sync-pull-verdict.shin this repository's CI and by the trial recorded on fix(template-sync): fail the run when the template pull fails #891.One thing surfaced on the way: the first attempt of the first run was marked failed by the signing step's branch readback, although the proposal and its signature were correct. That is a separate defect, tracked in #897, with a fix prepared.
🤖 Generated with Claude Code