On Wed, 12 Feb 2025 at 02:01, Olivier Lamy wrote:
>
> On Tue, 11 Feb 2025 at 23:57, Slawomir Jaranowski
> wrote:
> >
> > Hi,
> >
> > GitHub sends an announcement about the new version to subscribers on
> > GitHub project after publishing release.
> >
> > If we still need to send announcements to
On Tue, 11 Feb 2025 at 23:57, Slawomir Jaranowski
wrote:
>
> Hi,
>
> GitHub sends an announcement about the new version to subscribers on
> GitHub project after publishing release.
>
> If we still need to send announcements to annou...@maven.apache.org
> for some ASF formal reason
> maybe we can a
There are already some of notifications implements:
https://github.com/apache/infrastructure-asfyaml#notification-settings-for-repositories
If we accept such an idea we can ask infra about it or discover other
technical ways.
On Tue, 11 Feb 2025 at 15:15, tison wrote:
>
> This sounds great!
>
>
This sounds great!
For implementation, I can imagine a workflow triggered by a published
event [1], but I wonder how to send an email from within the workflow,
or use other forward methods.
[1]
https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trig
Hi,
GitHub sends an announcement about the new version to subscribers on
GitHub project after publishing release.
If we still need to send announcements to annou...@maven.apache.org
for some ASF formal reason
maybe we can automatically send it by GitHub ... what do you think?
--
Sławomir Jarano
