On 2020-03-31 12:48:28+0000, Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com> wrote:
> Our Azure Pipeline has served us well over the course of the past year or
> so, steadily catching issues before the respective patches hit the next 
> branch.
> 
> There is a GitHub-native CI system now, though, called "GitHub Actions"
> [https://github.com/features/actions] which is essentially on par with Azure
> Pipelines as far as our needs are concerned, and it brings a couple of
> advantages:
> 
>  * It is substantially easier to set up than Azure Pipelines: all you need
>    is to add the YAML-based build definition, push to your fork on GitHub,
>    and that's it.
>  * The syntax is a bit easier to read than Azure Pipelines'.
>  * We get more concurrent jobs (Azure Pipelines is limited to 10 concurrent
>    jobs).
> 
> With this change, users also no longer need to open a PR at 
> https://github.com/git/git or at https://github.com/gitgitgadget/git just to
> get the benefit of a CI build. They just push to their fork on GitHub and
> monitor the build. Easier than making apple pie.
> 
> The only caveat is that this will only work once the patch series makes it
> to master.

Github Actions also works in other branches, at least in pu:
https://github.com/sgn/git/runs/548975243?check_suite_focus=true

Anyway, this series will conflicts with my series for linux-musl CI.
And, Github Actions' Documentation job in pu failed because of missing
"curl-config".

Attached patches can be used to merge this series into pu.

-- 
Danh