zhangning21 commented on PR #19075:
URL: https://github.com/apache/nuttx/pull/19075#issuecomment-5035063197

   > @zhangning21 could you please add those information you added in the 
Summary into our CI Documentation: 
https://nuttx.apache.org/docs/latest/testing/nuttx-ci.html
   
   Thanks @acassis! Done — I've added the Summary details to the CI 
documentation
     you linked. There is now a new "Pull Request Dependencies" section in
     `Documentation/testing/nuttx-ci.rst` covering:
   
     - the supported `Depends-On:` declaration forms: one dependency per line 
or a
       single inline list, short `owner/repo/pull/N` references or full
       `https://github.com/...` URLs; the marker is case-insensitive, with
       `Depends-On:` used as the canonical spelling;
     - master-only behavior: declarations in release and backport PRs are 
ignored,
       preserving the existing matching-release-branch behavior;
     - ordered dependency handling, including how `Fetch-Source` fetches each 
valid
       dependency's head SHA and cherry-picks its commits into the matching 
checkout
       before the existing build matrix runs;
     - the three report/comment outcomes: `ok` with the fetched head SHAs, 
`invalid`
       when a `Depends-On:` marker is present but no valid dependency can be 
parsed,
       and `failed` when a valid dependency cannot be applied;
     - the edited-description gate and the intentional limitations: no 
dependency-PR
       state validation through the GitHub API, no automatic retrigger when a
       dependency PR changes, and no automated synchronized merge.
   
   The section renders like this on the CI docs page:
   
   <img width="738" height="1444" alt="image" 
src="https://github.com/user-attachments/assets/fa69373d-9e7a-4b75-bed5-069a28715dc4";
 />
   


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