Repository navigation
Conversation
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Important Review skippedAuto reviews are limited based on label configuration. 🚫 Review skipped — only excluded labels are configured.: 2
Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
|
Diagnostic complete: the same SHA/diff as fork PR #406 ran successfully from this internal branch in 2m39s. Evidence: https://github.com/openshift-hyperfleet/hyperfleet-api/actions/runs/39646086246 (event pull_request, PR #407, SHA 98582b1). This proves the job executes in the API repo, not that fork PR #406 triggered it. No code/settings changes or merge were made. Closing this temporary draft and removing only its diagnostic branch as agreed; the implementation remains in #406. |
Temporary diagnostic PR, explicitly authorized by Rafael. DO NOT MERGE.
This uses exactly the same existing commit as fork PR #406: 98582b1. No code, workflow, permission or repository setting is changed by this test. The only experimental difference is that this head branch belongs to openshift-hyperfleet/hyperfleet-api instead of the fork.
Goal: observe whether pull_request creates a pre-commit GitHub Actions run for an internal branch when the matching fork PR has no run. Capture run/check metadata and the SHA, then close this draft and delete only the temporary diagnostic branch. A run starting would narrow the issue to fork/event handling; no run would not by itself prove an organization policy or bootstrap requirement.
Tracked under https://redhat.atlassian.net/browse/HYPERFLEET-1806. The implementation/review PR remains #406.