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>
Junio C Hamano committed
May 25, 2026 at 11:58 UTC
7c9b38d267129625adeced9f66140e802c345261
1 file changed
+11
Documentation/SubmittingPatches
+11
@@ -792,6 +792,17 @@ relevant for debugging.
792
Then fix the problem and push your fix to your GitHub fork. This will
793
trigger a new CI build to ensure all tests pass.
794
795
+Even if you do not use GitHub CI to test your changes, pay close
796
+attention to new failures on the branches when the maintainer pushes
797
+out after your topic gets merged to the 'seen' branch to make sure
798
+that your topic is not breaking the CI, and retract your breaking
799
+topic quickly while you fix the breakage you caused.
800
+
801
+To see maintainer's push, keep an eye on this page:
802
+
803
+ `https://github.com/git/git/actions/workflows/main.yml?query=event%3Apush+actor%3Agitster`
804
+
805
+
806
[[mua]]
807
== MUA specific hints
808