Repository navigation
ci(repo): post the sync resolver comment when one artifact is downloaded - #7295
Merged
Merged
Conversation
download-artifact extracts a lone matching artifact into the path itself, so the publish step never found comment.md and posted nothing when the resolver declined a merge. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
🤖 AI Review
Both independent reviews reported no findings. Inspection of the diff and surrounding workflow code found no concrete issues: the fallback handles artifacts extracted into the download directory while preserving stage priority and downstream paths. No fundamental conflict with pending next-branch work was identified.
Findings
No issues found.
Stats
Claude findings: 0 · Codex findings: 0 · Confirmed: 0 · Refuted: 0 · Uncertain: 0
Models: claude-opus-5-5 + gpt-6.1-sol · Trigger: auto · Workflow run
This review runs once per PR. A maintainer can request another with a /ai-review comment.
jgoux
approved these changes
Nov 3, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Nov 3, 2026
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
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.
When the conflict resolver declines a develop-into-next merge, only the
sync-resolutionartifact exists.download-artifactextracts a lone matching artifact straight intosync-artifacts/instead ofsync-artifacts/sync-resolution/, so the publish step found nocomment.md. Because the resolve job succeeded, the failure fallback comment was skipped too. The job passed and the conflicting PR got no explanation, as seen on #7294.The publish step now falls back to
sync-artifacts/comment.mdwhen no per-artifact folder has one.🤖 Generated with Claude Code