andygrove opened a new pull request, #7352:
URL: https://github.com/apache/datafusion-comet/pull/7352

   ## Which issue does this PR close?
   
   No issue filed. Follow-up to #7311.
   
   ## Rationale for this change
   
   Since #7311, the PR tier for a fork pull request into `main` runs on the 
contributor's fork, and the `CI (fork)` check mirrors that run onto the pull 
request. When the fork has Actions disabled, the check reports **Enable CI on 
your fork**, which GitHub shows as a failure. Most forks have Actions disabled, 
because GitHub disables workflows on a new fork, so this check is now showing 
up on fork pull requests such as #7343. The guide covered the setup steps, but 
only one sentence covered this failure, and it did not say what the red check 
means for merging, what to run, or why a pull request opened before the change 
gets it too.
   
   ## What changes are included in this PR?
   
   - `ci.md`: a new "When the fork check finds no run" subsection under "Pull 
requests from forks". It explains the two messages (**Enable CI on your fork** 
and **No fork CI run for this commit**), says the check does not block merging 
but means the PR tier has not run, and gives the commands to fix it. It also 
notes that enabling Actions needs a new push, and covers pull requests opened 
before the change. The old one-sentence explanation now links to the 
subsection. The check's own details link still lands on "Pull requests from 
forks", directly above the new subsection.
   - `development.md`: the fork paragraph under "Submitting a Pull Request" now 
names the failing check and links to the subsection.
   
   ## How are these changes tested?
   
   Documentation only. Checked with prettier. The described behavior matches 
`fork_ci_status.yml` on `main`.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to