Repository navigation
ci: show verified bot update results in PR checks - #548
Merged
Merged
Conversation
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
1 participant
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.
Real bot PR #547 exposed a GitHub integration boundary: the explicit dispatches run and associate with the head, but the PR rollup remains empty while native bot PR workflows require approval. Publish one xpkgindex-update/ci commit status so review sees a pending/success/failure result and its evidence.
The default-branch proposal job waits for all four dispatched workflows on the exact head. Only four successful results and a fresh PR identity/head check can report success. Failure, cancellation, timeout or head mismatch cannot pass. The proposal summary/artifact links all actual runs. Existing statuses are not duplicated, and pending PRs can resume reporting. Only the proposal job gains statuses:write; builds stay read-only. No approval, automatic merge or deletion of native approval records is added.
Validation: 11 local integration/baseline tests cover exact-head completion, pending-to-success transitions, failure, cancellation, wrong head, timeout, status deduplication and prior PR/dispatch recovery. Ruff and Actionlint passed. A factual pending status on #547 confirmed that commit statuses appear in the PR rollup. All four real dispatched workflows for #547 are already successful; after merge, a fresh main Action will resume that bot PR and automatically publish its final result.