-
Notifications
You must be signed in to change notification settings - Fork 156
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
RFE: Silent mode #885
Comments
@sils1297 make sense, thanks. how about this (in merge:
quiet: true
|
@yegor256 I'd rather prefer a global setting for all commands plus also avoiding the command acknowledgements. I.e. the merge command should just merge with no comments at all. |
@sils1297 yeah, make sense. so it will be a global option ( quiet: true |
@sils1297 since there is no milestone yet I set it to "2.0" |
@yegor256 this is your task now,help us |
@yegor256 just an idea about how you can make it even cooler - provide the information while not doing comments: use the status API to set a rultor PR status. |
@alex-palevsky assign someone else pls |
@yegor256 -30 points to your rating :( |
@yegor256 got it, someone else will be assigned soon |
@alex-palevsky this is postponed. |
@original-brownbear OK, I put "postponed" label here |
@original-brownbear got it, someone else will be assigned soon |
People are getting a lot of emails in our project. GitHub's bad at regulating that. It would be nice to not have PR's and issues cluttered with unneeded comments. E.g. for a merge I get an email from github on merge anyways that rultor merged that stuff. Further flooding with "hey I'm doing a simple merge now like you requested" and "yep that worked" messages is not needed IMO. Zero messages on success, one message on failure would be my aim.
If I want to see the log one would probably need an additional log command or a parameter to the merge command (verbose=true).
Same probably also applies to releases.
The text was updated successfully, but these errors were encountered: