- User Since
- Jan 30 2017, 3:06 PM (234 w, 2 d)
Aug 29 2019
Also an example how "per-push notification" is implemented in Github events/webhooks:
I actually found my way here from discourse where the need for this was discussed:
Apr 25 2019
Gentle ping here again :) Has anyone managed to get a webhook triggered on a phabricator git repo, once-per-push, not once-per-each-commit ?
Apr 10 2019
ah, I missed that. I guess I should start testing this stuff soon :)
well, I'd say for example the "Close as <status> (only acts if task is not already closed)" is useful, and definitely needed.
Move the task to "done" column on the workboard, and the task automatically gets closed. That's handy.
Nov 26 2018
@jbrownEP Hey! Was this implemented yet? I'm interested in this feature aswell.. (being able to run hook action once per push, no matter how many commits there are in the push).
Mar 1 2017
Thanks for the detailed reply.
@epriestley : because it's easier to manage everything from a single instance of phabricator. Phabricator has native support for multiple authentication providers, so I don't see a problem with this.
@epriestley : we need multiple authentication providers because this is a shared phabricator instance, and thus different groups of users need different IDP.
Feb 23 2017
@epriestley: Yes, we have multiple authentication providers configured and needed in phabricator, and thus "allow auto login" won't work.