Am Donnerstag, 2. März 2017, 20:23:22 CET schrieb Maren Hachmann:
Am 02.03.2017 um 19:44 schrieb Christoffer Holmstedt:
2017-03-02 3:12 GMT+01:00 maren <marenhachmann@...36...
mailto:marenhachmann@...36...>:
Am 01.03.2017 um 22:19 schrieb Bryce Harrington:
On Tue, Feb 28, 2017 at 07:12:20PM -0800, Bryce Harrington wrote:
Thanks everyone who provided feedback on the plan to migrate to gitlab. I've updated the plan to incorporate all the feedback (see attached
diff
for what changed).
...cut...
Is the user experience acceptable?
- For me, it's fine - after Martin added a webhook that sends an email
with a diff on push events. I felt blind without that (but it seems to be the norm, it's the same on github).
...cut...
Maren
What do you mean with "push events"? Do you get an email with a diff for each commit to master?
- It's an email with a diff for the commits to any branch inside the
repo per 'git push'.
I don't know if commits that have been pushed together get a diff over all commits (but I think so - only I don't have any that contain more than one commit in my mail trash currently).
Email addresses for subscribers (currently) need to be added manually by someone who has access to the settings.
Wouldn't it make sense to set up a mailing list where only the gitlab server may send to, have gitlab send its push notifications there and allow people to just subscribe? That would use the already existing mailing list infrastructure and not require too much extra work.
Screenshot of one of the mails attached (no custom code needed to create them, it's pre-made, just need to activate the option in the settings at gitlab).
Regards, Maren
Tobias
Best regards
Christoffer Holmstedt
---- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel