kernel
/
git
mirror of https://git.kernel.org/pub/scm/git/git.git
1
0
Fork 0
Code Releases Activity

SubmittingPatches: proactively monitor GHCI pages 

Even those contributors who do not come from GGG and do not first
push their changes to their repositories on GitHub with CI enabled,
can still monitor the CI runs triggered by integration of their
topic to 'seen' and other branches to notice a breakage their topic
caused to the system.

Encourage them to help the project by keeping an eye on these CI
runs.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
main
Junio C Hamano 2026-05-25 11:58:48 +09:00
parent 67ad42147a
commit 7c9b38d267
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
Documentation/SubmittingPatches
View File

@ -792,6 +792,17 @@ relevant for debugging.
Then fix the problem and push your fix to your GitHub fork. This will
trigger a new CI build to ensure all tests pass.

Even if you do not use GitHub CI to test your changes, pay close
attention to new failures on the branches when the maintainer pushes
out after your topic gets merged to the 'seen' branch to make sure
that your topic is not breaking the CI, and retract your breaking
topic quickly while you fix the breakage you caused.

To see maintainer's push, keep an eye on this page:

`https://github.com/git/git/actions/workflows/main.yml?query=event%3Apush+actor%3Agitster`


[[mua]]
== MUA specific hints