All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH 1/1] README: adjust for final Azure Pipeline ID
Date: Sun, 24 Feb 2019 15:21:05 +0100 (STD)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.1902241520260.45@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqa7iloiwl.fsf@gitster-ct.c.googlers.com>

Hi Junio,

On Sat, 23 Feb 2019, Junio C Hamano wrote:

> "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
> writes:
> 
> > From: Johannes Schindelin <johannes.schindelin@gmx.de>
> >
> > During the six months of development of the Azure Pipelines support, the
> > patches went through quite a few iterations of changes, and to test
> > those iterations, a temporary build definition was used.
> >
> > In the meantime, Azure Pipelines support made it to `master`, and we now
> > have a regular Azure Pipeline, installed via the common GitHub App
> > workflow. This new pipeline has a different name (git.git instead of
> > test-git.git), and a new ID (11 instead of 2).
> >
> > Let's adjust the badge in our README to reflect that final shape of the
> > Azure Pipeline.
> 
> Always happy to see declaration of victory ;-).

Yep! I did take an internal victory lap, too.

Thank you for your help and your patience on this issue!

Ciao,
Dscho

> 
> >
> > Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
> > ---
> >  README.md | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/README.md b/README.md
> > index 764c480c66..88f126184c 100644
> > --- a/README.md
> > +++ b/README.md
> > @@ -1,4 +1,4 @@
> > -[![Build Status](https://dev.azure.com/git/git/_apis/build/status/test-git.git)](https://dev.azure.com/git/git/_build/latest?definitionId=2)
> > +[![Build Status](https://dev.azure.com/git/git/_apis/build/status/git.git)](https://dev.azure.com/git/git/_build/latest?definitionId=11)
> >  
> >  Git - fast, scalable, distributed revision control system
> >  =========================================================
> 

      reply	other threads:[~2019-02-24 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-23 14:49 [PATCH 0/1] Adjust the Azure Pipeline badge in our README Johannes Schindelin via GitGitGadget
2019-02-23 14:49 ` [PATCH 1/1] README: adjust for final Azure Pipeline ID Johannes Schindelin via GitGitGadget
2019-02-24  5:27   ` Junio C Hamano
2019-02-24 14:21     ` Johannes Schindelin [this message]

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=nycvar.QRO.7.76.6.1902241520260.45@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=gitster@pobox.com \
    /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.