Hi Emily, On Thu, 16 Apr 2020, Danh Doan wrote: > On 2020-04-15 20:45:05-0700, Elijah Newren <newren@xxxxxxxxx> wrote: > > > On Wed, Apr 15, 2020 at 7:01 PM Emily Shaffer > > <emilyshaffer@xxxxxxxxxx> wrote: > > > > > I'm curious to know how I can check this build method for myself for > > > next time. > > > > 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. > > For the time being, open a Github PR will trigger Azure Pipelines to Please spell it with an upper-case `H`: there is no `th` sound in GitHub. > check various things with both Linux, macOS, and Windows. > This Azure thing doesn't have that vs-build target, yet. More concretely, you will want to open a PR at https://github.com/git/git, not at https://github.com/gitgitgadget/git. For reasons (having to do with Junio's practice to base branches on older commits, where `azure-pipelines.yml` either does not exist, or needs changes to pass), the latter runs an Azure Pipeline on Pull Requests which is based _not_ on `azure-pipelines.yml`, but is essentially a manual re-implementation of it that does _not_ use YAML (but is revisioned separately), with manual patches for all kinds of issues on top that have made it into core Git's `master`. However, in your case I would strongly advise to simply use a throw-away branch, merge in the GitHub workflow patches by Danh and myself (as described in the quoted text below), and push it to your fork on GitHub. That will execute a workflow run that will show up at https://github.com/nasamuffin/git/actions/new. Ciao, Dscho > > We're moving to Github Actions. When that topic graduate to master, > we can simply branch out from master and push to our fork in GitHub, > it will run automatically. No need to create a PR on git.git anymore > > To check that vs-build target for the time being by merging > dd/ci-swap-azure-pipelines-with-github-actions > and push to your GitHub fork. > > -- > Danh > >
