raiden00pl opened a new pull request, #19855:
URL: https://github.com/apache/nuttx/pull/19855

   
   ## Summary
   
   The Depends-On feature (commit e73f7f7d0e) made the Build workflow
   trigger on PR description edits. A gate job checks whether the edit
   changed any Depends-On declaration: if yes, the build jobs run again
   with the new dependencies; on any other edit the gate skips all build
   jobs.
       
   The gate has a side effect that breaks PR check results. Skipped jobs
   still register check results on the PR, and the PR checks view shows
   the newest check run of each name. So after any description edit the
   PR shows "skipped" for every build check instead of the pass/fail
   from the real run. Re-running that newest run only repeats the skip,
   so the real results never come back. This can also hide a red X from
   a failed build.
       
   Fix by not triggering Build on description edits at all: remove the
   "edited" event type and the gate job.
       
   Depends-On keeps working: dependencies are read from the description
   at the start of every run against master, as before. Fetch-Source now
   re-reads the description through the API instead of using the copy
   stored in the event payload, so every run uses the current Depends-On
   state no matter how it was triggered.
       
   After editing a Depends-On line, retrigger CI by any of:
       - pushing new or rebased commits to the PR branch
       - closing and reopening the PR
       - pressing "Re-run all jobs" on the existing Build run
       
   A description edit alone no longer triggers anything, which is
   exactly the behavior that corrupted the PR check results.
       
   Same change as in nuttx-apps; both repos received the gate from the
   same Depends-On feature.
   
   ## Impact
   
   try to fix https://github.com/apache/nuttx/pull/19673#issuecomment-5301374789
   
   ## Testing
   
   none, must be checked upstream


-- 
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]

Reply via email to