-
Notifications
You must be signed in to change notification settings - Fork 491
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve silence page #1111
Improve silence page #1111
Conversation
b21330f
to
1ad6bbd
Compare
Could you achieve the same goal by setting the user field to "bot"? |
We will likely have multiple bots, and we will probably want to distinguish On Wed, Jul 1, 2015 at 12:17 PM, Matt Jibson notifications@github.com
|
Well then each can set their own username. My point is that I'm not completely convinced this solution (an extra isBot boolean) is the best solution for the problem. If we can use an existing field to achieve the same goal, will that work? |
+1 on using an existing field. We can use a naming prefix for bots, and add search with globs if we want filtering |
The main reason I don't like this idea is that is a convention that needs On Wed, Jul 1, 2015 at 2:02 PM, Greg Bray notifications@github.com wrote:
|
We've been down this road before though with isEmail/isPost/isDashboard/isWhatever in rendering alert templates. This method has a lot more flexibility and no additional coding/maintenance. We already have a lot of conventions, and if a human does something wrong we can address that. Or if someone else wants to change how it works they can come up with their own convention. If you really want an isBot, that should be an attribute on an actual user profile/record, which is something we can address when adding authentication and user management. In my mind it doesn't make much sense to tack it on to the silence item/event. |
Anyone object to merging this now? We can do further improvements in another PR. |
1ad6bbd
to
1d765ef
Compare
No objections here. I'm sure we'll have more improvements to that page soon. |
1d765ef
to
4f4cfb6
Compare
4f4cfb6
to
6bcc566
Compare
No description provided.