From: Jeff King <peff@peff.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Emily Shaffer <emilyshaffer@google.com>, git@vger.kernel.org
Subject: Re: GitGitGadget on git/git, was Re: Should we auto-close PRs on git/git?
Date: Mon, 25 Nov 2019 09:30:23 -0500 [thread overview]
Message-ID: <20191125143023.GF494@sigill.intra.peff.net> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1911221430510.31080@tvgsbejvaqbjf.bet>
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).
> All I need is to install the app:
> [...]
> ... which I just did.
Very cool. :)
-Peff
next prev parent reply other threads:[~2019-11-25 14:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 2:00 Should we auto-close PRs on git/git? Emily Shaffer
2019-11-09 4:55 ` Junio C Hamano
2019-11-13 5:29 ` Stephen Smith
2019-11-12 19:11 ` Johannes Schindelin
2019-11-13 1:10 ` Jeff King
2019-11-13 12:04 ` Johannes Schindelin
2019-11-14 7:41 ` Jeff King
2019-11-14 23:03 ` Johannes Schindelin
2019-11-18 18:37 ` GitGitGadget on git/git, was " Johannes Schindelin
2019-11-21 10:54 ` Jeff King
2019-11-22 13:50 ` Johannes Schindelin
2019-11-22 14:43 ` Johannes Schindelin
2019-11-25 14:30 ` Jeff King [this message]
2019-11-26 20:55 ` Johannes Schindelin
2019-11-26 21:56 ` Eric Wong
2019-11-26 22:22 ` Johannes Schindelin
2019-11-26 22:40 ` Eric Wong
2019-11-26 22:52 ` Johannes Schindelin
2019-11-26 23:58 ` Eric Wong
2019-11-27 1:52 ` Junio C Hamano
2019-11-27 2:37 ` Eric Wong
2019-11-13 21:09 ` Emily Shaffer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191125143023.GF494@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.