Hi Peff, On Mon, 25 Nov 2019, Jeff King wrote: > On Fri, Nov 22, 2019 at 02:50:05PM +0100, Johannes Schindelin wrote: > > > > Wow, thanks for working on this! I don't know that I'd call my > > > javascript skills even rudimentary, but I did give it a look. The real > > > challenge to me is not the individual lines of code, but understanding > > > how the Azure Pipelines and GitHub App systems fit together. So I didn't > > > see anything wrong, but I also know very little about those systems. > > > > I actually spent some quality time with the wiki in the past days to > > remedy that. You can adore the result in all its beauty here: > > > > https://github.com/gitgitgadget/gitgitgadget/wiki/GitGitGadget's-Azure-Function-and-Azure-Pipelines > > Thanks, this was very informative. I have a feeling that some of this > could be done via the new Actions stuff that GitHub has been shipping, > but I have no idea if it would make any of it easier (and certainly I'm > not advocating dropping a working system to chase a new shiny toy). It is tempting all right. The biggest obstacle is that at least one of those Pipelines requires access to a clone of public-inbox.org/git, and cloning that is rather expensive. Even a shallow fetch would be super expensive, by virtue of _all_ the mails being blobs reachable from the tip commit's tree. Further, GitHub Actions' triggers are a bit too limited: I want this Pipeline to trigger when public-inbox.org/git is updated, not when any branch in gitgitgadget/git is updated. So yes, while it is tempting, it is also not possible right now to use GitHub Actions. Ciao, Dscho
