This is a late-re-roll of this v2: https://lore.kernel.org/git/cover-0.3-0000000000-20210607T110044Z-avarab@xxxxxxxxx/ I fixed the problems Đoàn Trần Công Danh and SZEDER Gábor pointed out in v2. I ejected the removal of the inline patch for Pine from this verison. Johannes suggest another approach in https://lore.kernel.org/git/nycvar.QRO.7.76.6.2106072346560.55@xxxxxxxxxxxxxxxxx/ I think we're spending way too much reader time on [Al]pine still, but I don't want to write something that's accurate advice for an E-Mail client I've never used, so I'm dropping it. Perhaps someone else will pick that cleanup up... Ævar Arnfjörð Bjarmason (2): SubmittingPatches: move discussion of Signed-off-by above "send" SubmittingPatches: replace discussion of Travis with GitHub Actions Documentation/SubmittingPatches | 207 +++++++++++++++----------------- 1 file changed, 96 insertions(+), 111 deletions(-) Range-diff against v2: 1: 6e2749d307 = 1: 4283f000c5 SubmittingPatches: move discussion of Signed-off-by above "send" 2: 788b198520 ! 2: ecb9924a6a SubmittingPatches: replace discussion of Travis with GitHub Actions @@ Documentation/SubmittingPatches: the feature triggers the new behavior when it s -GitHub-Travis CI hints section for details. +Pushing to a fork of https://github.com/git/git will use their CI +integration to test your changes on Linux, Mac and Windows. See the -+GitHub CI section for details. ++<<GHCI,GitHub CI>> section for details. Do not forget to update the documentation to describe the updated behavior and make sure that the resulting documentation set formats @@ Documentation/SubmittingPatches: their trees themselves. + entitled "What's cooking in git.git" and "What's in git.git" giving the status of various proposed changes. - [[travis]] +-[[travis]] -== GitHub-Travis CI hints -+== GitHub CI ++== GitHub CI[[GHCI]]] -With an account at GitHub (you can get one for free to work on open -source projects), you can use Travis CI to test your changes on Linux, @@ Documentation/SubmittingPatches: Follow these steps for the initial setup: - -. Open your Travis CI profile page: https://travis-ci.org/profile - - . Enable Travis CI builds for your Git fork. - - After the initial setup, Travis CI will run whenever you push new changes +-. Enable Travis CI builds for your Git fork. +- +-After the initial setup, Travis CI will run whenever you push new changes ++After the initial setup, CI will run whenever you push new changes to your fork of Git on GitHub. You can monitor the test state of all your -branches here: https://travis-ci.org/__<Your GitHub handle>__/git/branches +branches here: https://github.com/<Your GitHub handle>/git/actions/workflows/main.yml 3: fecc3459f1 < -: ---------- SubmittingPatches: remove pine-specific hints from MUA hints -- 2.32.0.957.gd9e39d72fe6
