Run CI when copy-pr-bot creates PR refs#9
Closed
pnwamk wants to merge 3 commits into
Closed
Conversation
copy-pr-bot creates pull-request/N refs when PRs open, but the CI workflow only watched push events. A branch create event can therefore leave a PR with no checks until a later update pushes the mirror ref. Trigger CI on create events and gate the root jobs so only pull-request/N branch creation starts the matrix. Later mirror pushes, main pushes, tags, and manual dispatch keep the existing behavior.
Collaborator
Author
|
/ok to test 50eac4f |
nv-asrikanth
previously approved these changes
May 7, 2026
The create-event experiment proved that CI can run on copy-pr-bot's pull-request/N refs, but GitHub does not associate those check suites with the actual pull request. That leaves the PR page without visible checks even when the workflow succeeds. Add a pull_request trigger for PRs targeting main so GitHub attaches the check suite to the PR head branch. Keep the existing push triggers for pull-request/N mirror updates, main, tags, and manual dispatch.
Remove the temporary pull_request trigger that was added to test GitHub's PR check association behavior. CompileIQ's intended PR CI path is still copy-pr-bot updating pull-request/N refs and Actions running from those push events. Keeping full CI off direct pull_request events preserves the copy-pr-bot approval gate while we debug why the first manual /ok to test copy is not producing the expected push workflow run.
Collaborator
Author
|
This PR was investigative to try and learn more about why copy-pr-bot seems to miss running CI for a PR. Summary from the investigation:
Closing this ticket. |
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 hypothesis for why CI appears to not run on PRs at the moment when expected:
copy-pr-botcreatespull-request/Nrefs when a PR opens, but the CI workflow is only configured currently to watchpushevents. A branch create event can therefore leave a PR with no checks until a later update pushes the mirror ref.This PR changes that in an attempt to fix the issue (CI should run here successfully if the hypothesis is correct) by adding watch on the
createevent as well (but checks are added to ensure we do not run the CI on ANY branch creation event, it needs to be a pull-request branch).