[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Gitlab (commit) notifications
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2020-05-22 9:11:15
Message-ID: CA+XidOGf3EuVTCqh14PkGBS0=CeHOGe+7Gkxs+Sez62zujVQDQ () mail ! gmail ! com
[Download RAW message or body]

On Thu, May 21, 2020 at 11:50 PM Thomas Baumgart <thb@net-bembel.de> wrote:
>
> On Donnerstag, 21. Mai 2020 11:54:15 CEST Ben Cooksley wrote:
>
> > On Thu, May 21, 2020 at 9:43 PM Thomas Friedrichsmeier
> > <thomas.friedrichsmeier@ruhr-uni-bochum.de> wrote:
> > >
> > > Am Thu, 21 May 2020 20:16:22 +1200
> > > schrieb Ben Cooksley <bcooksley@kde.org>:
> > > > On Thu, May 21, 2020 at 12:20 AM Thomas Friedrichsmeier
> > > > <thomas.friedrichsmeier@ruhr-uni-bochum.de> wrote:
> > > [...]
> > > > > Is there any self-service way to receive commit/push notifications
> > > > > via email from gitlab?
> > > > >
> > > > > If so, would such notifications include work-branches (that would be
> > > > > useful, IMO)?
> > > >
> > > > Work branches cannot be notified on, as otherwise you end up
> > > > renotifying all of the new commits in that work branch every time you
> > > > force push.
> > > > (It is impossible for hooks to tell if you are pushing a rewritten
> > > > commit or a new one)
> > >
> > > Ok, I can live with that (I don't intend to make use of force-pushing,
> > > anyway, and may just switch to a different prefix, where appropriate).
> > >
> > > However, I'd certainly welcome a feature to have commit notifications
> > > on non-"work" branches (without merge requests). In RKWard we used to
> > > have commit notifications going to a dedicated mailing list
> > > (rkward-tracker) that also receives build failure notifications and
> > > such, for a single point to subscribe to "all the noise" for the
> > > project. IIRC, that notification mechanism was set up for us by
> > > sysadmin, not by self-service.
> >
> > For all non-work branches, emails will be sent to kde-commits@kde.org
> > - so these already exist.
> > What doesn't exist is a way to selectively subscribe to this list
> > (that is, for a given project only)
> >
> > Should someone be interested in building a commit filter type service,
> > please get in touch.
>
>
> Would it be feasible to use Mailman "topics" for that?

Potentially, but there would be limited success to using it that way
as we would need to add a 'topic' for every repository - which isn't
particularly sustainable, and is still very limited in the filtering
capabilities on offer.

Cheers,
Ben

>
>
> --
>
> Regards
>
> Thomas Baumgart
>
> https://www.signal.org/       Signal, the better WhatsApp
> -------------------------------------------------------------
> 'Good code is not created, it evolves.'
> -- George Anzinger
> -------------------------------------------------------------
[prev in list] [next in list] [prev in thread] [next in thread]