Re: [PATCH 2/3] SubmittingPatches: replace discussion of Travis with GitHub Actions

From: "Đoàn Trần Công Danh" <congdanhqx@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>
Subject: Re: [PATCH 2/3] SubmittingPatches: replace discussion of Travis with GitHub Actions
Date: Wed, 12 May 2021 19:24:14 +0700	[thread overview]
Message-ID: <YJvI7hCoaIXkkDyl@danh.dev> (raw)
In-Reply-To: <patch-2.3-7add00cc87-20210512T084137Z-avarab@gmail.com>

On 2021-05-12 10:45:01+0200, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
>  If a branch did not pass all test cases then it is marked with a red
> -cross.  In that case you can click on the failing Travis CI job and
> -scroll all the way down in the log.  Find the line "<-- Click here to see
> -detailed test output!" and click on the triangle next to the log line
> -number to expand the detailed test output.  Here is such a failing
> -example: https://travis-ci.org/git/git/jobs/122676187
> -
> -Fix the problem and push your fix to your Git fork.  This will trigger
> -a new Travis CI build to ensure all tests pass.
> +cross. In that case you can click on the failing job and navigate to
> +"ci/run-build-and-tests.sh" and/or "ci/print-test-failures.sh". You
> +can also download "Artifacts" which are tarred (or zipped) archives
> +with test data relevant for debugging.
> +
> +Then fix the problem and push your fix to your Github fork. This will

Nit: s/Github/GitHub/

It's the brand.

-- 
Danh