Re: [PATCH] githubci: add a workflow for creating GitHub release notes
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Dec 5, 2021, 01:25 UTC
- Message-ID
- <xmqqo85vonba.fsf@gitster.g>
- In-Reply-To
- <20211203083334.tziwuhbg2u4lsslt@fs>
Fabian Stelzer <fs@gigacodes.de> writes:
Show 5 quoted lines
> 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?