Emily Shaffer <emilyshaffer@xxxxxxxxxx> writes: > On Wed, Apr 15, 2020 at 08:45:05PM -0700, Elijah Newren wrote: >> >> Create a fork of github.com/git/git and open a pull request against >> it. (I believe you could also fork github.com/gitgitgadget/git and do >> a pull request against it, but I switched over to /git/git a while >> ago.) Immediately upon opening the pull request, a bunch of linux, >> mac, windows, and freebsd builds will be triggered with various runs >> of the testsuite. Has been very useful for catching issues for me >> before I sent them off to the list. > > I did before I sent this iteration, and it passed: > https://github.com/gitgitgadget/git/pull/573 > > That's why I'm confused :) Did I do something differently? I don't use > GGG to send the emails, but I do use it to run CI checks. Comparing the list of "checks" revealed by clicking "Show all checks" there, with the list of "Actions" with recent tip of 'pu', say, https://github.com/git/git/actions/runs/79416884, I notice that the former does not have vs-build. Also, the former seems to be on "Azure Pipelines" (e.g. [*1*] which is "Windows build" among the "checks" on the list), while the latter is "Github Actions" (e.g. [*2*], among which exists "VS-build" that seems to be missing from the former). The latter is coming from having the dd/ci-swap-azure-pipelines-with-github-actions topic and other two topics that it depends on, which are right now only in 'pu'. As we'd like to advance the Github Actions CI support to 'next', I've been looking at the failures to it caused by individual topics (and right now, we know of two topics, one is the bugreport and the other is reftable) to make sure these other topics can enter 'next'. Thanks. [References] *1* https://github.com/gitgitgadget/git/pull/573/checks?check_run_id=565642291 *2* https://github.com/git/git/runs/590781044?check_suite_focus=true
