From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>,
"Dave Huseby" <dwh@linuxprogrammer.org>,
"Lars Schneider" <larsxschneider@gmail.com>,
"Đoàn Trần Công Danh" <congdanhqx@gmail.com>,
"Felipe Contreras" <felipe.contreras@gmail.com>
Subject: Re: [PATCH v2 2/3] SubmittingPatches: replace discussion of Travis with GitHub Actions
Date: Mon, 7 Jun 2021 19:25:42 +0200 [thread overview]
Message-ID: <20210607172542.GA6312@szeder.dev> (raw)
In-Reply-To: <patch-2.3-7d5d2854e3-20210607T110044Z-avarab@gmail.com>
On Mon, Jun 07, 2021 at 01:03:42PM +0200, Ævar Arnfjörð Bjarmason wrote:
> Replace the discussion of Travis CI added in
> 0e5d028a7a0 (Documentation: add setup instructions for Travis CI,
> 2016-05-02) with something that covers the GitHub Actions added in
> 889cacb6897 (ci: configure GitHub Actions for CI/PR, 2020-04-11).
>
> The setup is trivial compared to using Travis, and it even works on
> Windows (that "hopefully soon" comment was probably out-of-date on
> Travis as well).
>
> Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
> ---
> Documentation/SubmittingPatches | 44 ++++++++++++---------------------
> 1 file changed, 16 insertions(+), 28 deletions(-)
>
> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> index 2643062624..e372d17673 100644
> --- a/Documentation/SubmittingPatches
> +++ b/Documentation/SubmittingPatches
> @@ -74,10 +74,9 @@ the feature triggers the new behavior when it should, and to show the
> feature does not trigger when it shouldn't. After any code change, make
> sure that the entire test suite passes.
>
> -If you have an account at GitHub (and you can get one for free to work
> -on open source projects), you can use their Travis CI integration to
> -test your changes on Linux, Mac (and hopefully soon Windows). See
> -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.
>
> Do not forget to update the documentation to describe the updated
> behavior and make sure that the resulting documentation set formats
> @@ -451,12 +450,12 @@ their trees themselves.
> the status of various proposed changes.
>
> [[travis]]
What about this occurence of "travis"?
> -== GitHub-Travis CI hints
> +== GitHub CI
>
> -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,
> -Mac (and hopefully soon Windows). You can find a successful example
> -test build here: https://travis-ci.org/git/git/builds/120473209
> +With an account at GitHub, you can use GitHub CI to test your changes
> +on Linux, Mac and Windows. See
> +https://github.com/git/git/actions/workflows/main.yml for examples of
> +recent CI runs.
>
> Follow these steps for the initial setup:
>
> @@ -464,31 +463,20 @@ Follow these steps for the initial setup:
> You can find detailed instructions how to fork here:
> https://help.github.com/articles/fork-a-repo/
>
> -. Open the Travis CI website: https://travis-ci.org
> -
> -. Press the "Sign in with GitHub" button.
> -
> -. Grant Travis CI permissions to access your GitHub account.
> - You can find more information about the required permissions here:
> - https://docs.travis-ci.com/user/github-oauth-scopes
> -
> -. 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
And what about these two mentions of Travis CI in the context?
> 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
next prev parent reply other threads:[~2021-06-07 17:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 8:44 [PATCH 0/3] SubmittingPatches: a few unrelated minor fixes Ævar Arnfjörð Bjarmason
2021-05-12 8:45 ` [PATCH 1/3] SubmittingPatches: move discussion of Signed-off-by above "send" Ævar Arnfjörð Bjarmason
2021-05-12 9:29 ` Felipe Contreras
2021-06-07 11:02 ` Ævar Arnfjörð Bjarmason
2021-06-07 16:16 ` Felipe Contreras
2021-05-12 8:45 ` [PATCH 2/3] SubmittingPatches: replace discussion of Travis with GitHub Actions Ævar Arnfjörð Bjarmason
2021-05-12 12:24 ` Đoàn Trần Công Danh
2021-05-12 22:40 ` Junio C Hamano
2021-05-12 8:45 ` [PATCH 3/3] SubmittingPatches: remove pine-specific hints from MUA hints Ævar Arnfjörð Bjarmason
2021-05-12 23:51 ` Dave Huseby
2021-05-13 6:38 ` Felipe Contreras
2021-05-13 14:45 ` Dave Huseby
2021-05-13 20:08 ` Felipe Contreras
2021-05-17 19:05 ` Dave Huseby
2021-05-13 7:50 ` Ævar Arnfjörð Bjarmason
2021-05-13 14:42 ` Dave Huseby
2021-06-07 11:03 ` [PATCH v2 0/3] SubmittingPatches: a few unrelated minor fixes Ævar Arnfjörð Bjarmason
2021-06-07 11:03 ` [PATCH v2 1/3] SubmittingPatches: move discussion of Signed-off-by above "send" Ævar Arnfjörð Bjarmason
2021-06-07 15:58 ` Đoàn Trần Công Danh
2021-06-07 11:03 ` [PATCH v2 2/3] SubmittingPatches: replace discussion of Travis with GitHub Actions Ævar Arnfjörð Bjarmason
2021-06-07 17:25 ` SZEDER Gábor [this message]
2021-06-07 11:03 ` [PATCH v2 3/3] SubmittingPatches: remove pine-specific hints from MUA hints Ævar Arnfjörð Bjarmason
2021-06-07 21:49 ` Johannes Schindelin
2021-06-08 3:50 ` [PATCH v2 0/3] SubmittingPatches: a few unrelated minor fixes Junio C Hamano
2021-07-22 12:11 ` [PATCH v3 0/2] SubmittingPatches: talk about GitHub CI, not Travis + move-only Ævar Arnfjörð Bjarmason
2021-07-22 12:11 ` [PATCH v3 1/2] SubmittingPatches: move discussion of Signed-off-by above "send" Ævar Arnfjörð Bjarmason
2021-07-23 6:36 ` Bagas Sanjaya
2021-07-22 12:11 ` [PATCH v3 2/2] SubmittingPatches: replace discussion of Travis with GitHub Actions Ævar Arnfjörð Bjarmason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210607172542.GA6312@szeder.dev \
--to=szeder.dev@gmail.com \
--cc=avarab@gmail.com \
--cc=congdanhqx@gmail.com \
--cc=dwh@linuxprogrammer.org \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=larsxschneider@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).