From: Junio C Hamano <gitster@pobox•com>
To: Fabian Stelzer <fs@gigacodes•de>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx•de>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail•com>,
"Matthias Aßhauer" <mha1993@live•de>,
"Mahdi Hosseinzadeh via GitGitGadget" <gitgitgadget@gmail•com>,
git@vger•kernel.org,
"Mahdi Hosseinzadeh" <mdihosseinzadeh@gmail•com>
Subject: Re: [PATCH] githubci: add a workflow for creating GitHub release notes
Date: Sat, 04 Dec 2021 17:25:13 -0800 [thread overview]
Message-ID: <xmqqo85vonba.fsf@gitster.g> (raw)
In-Reply-To: <20211203083334.tziwuhbg2u4lsslt@fs> (Fabian Stelzer's message of "Fri, 3 Dec 2021 09:33:34 +0100")
Fabian Stelzer <fs@gigacodes•de> writes:
> One benefit that I see is that github offers APIs & Notifications
> around releases and lots of CI integration already exist for it. If my
> (non github) CI includes building the git source then i can easily
> trigger when upstream releases a new version. Just pulling the repo
> and watching for the tag works just as well of course.
Ahh, thanks.
If some sort of "push" notification is available only for "there is
a new release" but not for "there is a new tag", then I can sort of
see why having a "release" would be nice. Listening to notifications
and acting on them is more pleasant than having to poll.
Do I understand what you said correctly?
next prev parent reply other threads:[~2021-12-05 1:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 11:36 [PATCH] githubci: add a workflow for creating GitHub release notes Mahdi Hosseinzadeh via GitGitGadget
2021-11-25 20:57 ` Matthias Aßhauer
2021-11-26 13:59 ` Johannes Schindelin
2021-11-26 17:37 ` Matthias Aßhauer
2021-11-29 12:49 ` Ævar Arnfjörð Bjarmason
2021-11-30 11:46 ` Johannes Schindelin
2021-12-02 19:05 ` Junio C Hamano
2021-12-03 8:33 ` Fabian Stelzer
2021-12-05 1:25 ` Junio C Hamano [this message]
2021-12-05 10:54 ` Fabian Stelzer
2021-12-07 0:05 ` Junio C Hamano
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=xmqqo85vonba.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=avarab@gmail$(echo .)com \
--cc=fs@gigacodes$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=gitgitgadget@gmail$(echo .)com \
--cc=mdihosseinzadeh@gmail$(echo .)com \
--cc=mha1993@live$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox