Skip to content

ci(repo): post the sync resolver comment when one artifact is downloaded - #7295

Open
avallete wants to merge 1 commit into
developfrom
avallete/ci-bot-fix-verification-613a7c
Open

avallete wants to merge 1 commit into
developfrom
avallete/ci-bot-fix-verification-613a7c

Conversation

@avallete

Copy link
Copy Markdown
Member

When the conflict resolver declines a develop-into-next merge, only the sync-resolution artifact exists. download-artifact extracts a lone matching artifact straight into sync-artifacts/ instead of sync-artifacts/sync-resolution/, so the publish step found no comment.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.md when no per-artifact folder has one.

🤖 Generated with Claude Code

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>
@avallete
avallete requested review from a team and supabase-oss as code owners October 23, 2026 09:44

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 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.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant