Re: Gitlab (commit) notifications
Em 21/05/2020 10:11, Filipe Saraiva escreveu: > Em 20/05/2020 09:19, Thomas Friedrichsmeier escreveu: >> Hi! >> >> Is there any self-service way to receive commit/push notifications via >> email from gitlab? >> > > Gitlab provides an Atom feed for commits in each branch. Visit the > commits page for the project branch and you will see the feed button in > the right side of the filter input text. > Alternatively, Gitlab provides an atom feed for combined activities like push/commits events for master and feature branches (including creation and deletion of feature branches), and comments/open/close events of issues and merge requests. Visit an Activity page of a project (project page, right-side bar: Project Overview > Activity) and you will see a feed button with the link to subscribe. Despite this page can filter the presented activities (only Push events, only Merge events, ...), the feed is only for all combined events. As an example, the activity page of Cantor: https://invent.kde.org/education/cantor/activity You also can access feeds changing the $variables in the follow link: https://invent.kde.org/$NAMESPACE/$PROJECT.atom Using Cantor as example again: https://invent.kde.org/education/cantor.atom Cheers; -- Filipe Saraiva http://filipesaraiva.info/ signature.asc Description: OpenPGP digital signature
Re: Gitlab (commit) notifications
El dijous, 21 de maig de 2020, a les 15:11:48 CEST, Filipe Saraiva va escriure: > Em 20/05/2020 09:19, Thomas Friedrichsmeier escreveu: > > Hi! > > > > Is there any self-service way to receive commit/push notifications via > > email from gitlab? > > > > Gitlab provides an Atom feed for commits in each branch. Visit the > commits page for the project branch and you will see the feed button in > the right side of the filter input text. > > For example, see the feed button in Cantor commits page for master > branch: https://invent.kde.org/education/cantor/-/commits/master FWIW I've used that feed with some non-Free service that watches the RSS for me and sends me an email when there's new entries on the RSS. Seems to work relatively well for now, relies on a non-Free service but i guess until we get a better solution i can live with them knowing i'm interested in KDE development. Cheers, Albert > > I hope it can help you or be a workaround. > > Cheers; > >
Re: Gitlab (commit) notifications
On Thu, May 21, 2020 at 11:50 PM Thomas Baumgart wrote: > > On Donnerstag, 21. Mai 2020 11:54:15 CEST Ben Cooksley wrote: > > > On Thu, May 21, 2020 at 9:43 PM Thomas Friedrichsmeier > > wrote: > > > > > > Am Thu, 21 May 2020 20:16:22 +1200 > > > schrieb Ben Cooksley : > > > > On Thu, May 21, 2020 at 12:20 AM Thomas Friedrichsmeier > > > > 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-comm...@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 > -
Re: Gitlab (commit) notifications
Em 20/05/2020 09:19, Thomas Friedrichsmeier escreveu: > Hi! > > Is there any self-service way to receive commit/push notifications via > email from gitlab? > Gitlab provides an Atom feed for commits in each branch. Visit the commits page for the project branch and you will see the feed button in the right side of the filter input text. For example, see the feed button in Cantor commits page for master branch: https://invent.kde.org/education/cantor/-/commits/master I hope it can help you or be a workaround. Cheers; -- Filipe Saraiva http://filipesaraiva.info/ signature.asc Description: OpenPGP digital signature
Re: Gitlab (commit) notifications
On Donnerstag, 21. Mai 2020 11:54:15 CEST Ben Cooksley wrote: > On Thu, May 21, 2020 at 9:43 PM Thomas Friedrichsmeier > wrote: > > > > Am Thu, 21 May 2020 20:16:22 +1200 > > schrieb Ben Cooksley : > > > On Thu, May 21, 2020 at 12:20 AM Thomas Friedrichsmeier > > > 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-comm...@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? -- Regards Thomas Baumgart https://www.signal.org/ Signal, the better WhatsApp - 'Good code is not created, it evolves.' -- George Anzinger - signature.asc Description: This is a digitally signed message part.
Re: Gitlab (commit) notifications
On Thu, May 21, 2020 at 9:43 PM Thomas Friedrichsmeier wrote: > > Am Thu, 21 May 2020 20:16:22 +1200 > schrieb Ben Cooksley : > > On Thu, May 21, 2020 at 12:20 AM Thomas Friedrichsmeier > > 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-comm...@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. > > Not exactly a high-priority thing, but I for one would welcome this > feature. > > Regards > Thomas Cheers, Ben
Re: Gitlab (commit) notifications
Am Thu, 21 May 2020 20:16:22 +1200 schrieb Ben Cooksley : > On Thu, May 21, 2020 at 12:20 AM Thomas Friedrichsmeier > 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. Not exactly a high-priority thing, but I for one would welcome this feature. Regards Thomas pgpiK7e2DtQq4.pgp Description: Digitale Signatur von OpenPGP
Re: Gitlab (commit) notifications
On Wednesday, 20 May 2020 14:19:13 CEST Thomas Friedrichsmeier wrote: > Is there any self-service way to receive commit/push notifications via > email from gitlab? > You can find specific information: https://invent.kde.org/help/user/profile/ notifications. If you go for the "Watch" option I would suggest to filter via the header: X- GitLab-Commit-ID. But I will leave that to your preferences ;-) Best, -- Marc Deop i Argemà System Engineer
Re: Gitlab (commit) notifications
On Thu, May 21, 2020 at 6:21 AM Albert Astals Cid wrote: > > El dimecres, 20 de maig de 2020, a les 14:57:06 CEST, Nate Graham va escriure: > > If you click on a repo's bell icon and set your notification status to > > "Watch", it will email you when an MR is merged. > > Unfortunately that doesn't work for pushes. For that you want something like the commit filter we used to have many years back. > > I tried looking in gitlab bug tracker for a feature request about it, but > since gitlab's bug tracker is impossible to navigate because of how many > closings, duplicates, huge migrations between products, etc. they have done i > got lost. > > Cheers, > Albert Cheers, Ben > > > > > Nate > > > > > > On 5/20/20 6:19 AM, Thomas Friedrichsmeier wrote: > > > Hi! > > > > > > 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)? > > > > > > Regards > > > Thomas > > > > > > > > >
Re: Gitlab (commit) notifications
On Thu, May 21, 2020 at 12:20 AM Thomas Friedrichsmeier wrote: > > Hi! > > 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) > > Regards > Thomas Cheers, Ben
Re: Gitlab (commit) notifications
El dimecres, 20 de maig de 2020, a les 14:57:06 CEST, Nate Graham va escriure: > If you click on a repo's bell icon and set your notification status to > "Watch", it will email you when an MR is merged. Unfortunately that doesn't work for pushes. I tried looking in gitlab bug tracker for a feature request about it, but since gitlab's bug tracker is impossible to navigate because of how many closings, duplicates, huge migrations between products, etc. they have done i got lost. Cheers, Albert > > Nate > > > On 5/20/20 6:19 AM, Thomas Friedrichsmeier wrote: > > Hi! > > > > 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)? > > > > Regards > > Thomas > > >
Re: Gitlab (commit) notifications
If you click on a repo's bell icon and set your notification status to "Watch", it will email you when an MR is merged. Nate On 5/20/20 6:19 AM, Thomas Friedrichsmeier wrote: Hi! 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)? Regards Thomas
