On Thu, Jul 14 2022, Junio C Hamano wrote: > "Johannes Schindelin via GitGitGadget" <gitgitgadget@xxxxxxxxx> > writes: > >> Unfortunately, I noticed this regression no earlier than when I needed >> to validate Git for Windows v2.37.1. Since v2.37.1 was an embargoed >> release, I could not use GitHub Actions for the CI testing, so I had to >> reinstate Git's Azure Pipeline. > > I wonder if it would make your life easier if the same GitHub > Actions CI stuff were available for the Cabal repository we use for > embargoed work, by allowing you to use the same validation for usual > releases and the enbargoed ones? Isn't it. Looking at e.g. https://github.com/git/cabal/actions/runs/2284056293 (private link) that's the CI run for the latest push to "master" (same as https://github.com/git/git/commit/e8005e4871f130c4e402ddca2032c111252f070a). So I didn't get this idea that we must have Azure to resurrect for "private CI", don't we have that already, and anyone can use it by re-pushing git.git to a private repo (the limitation being that on GitHub you can't make a private fork of a public repo)?
