-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
Bot locking "as resolved" #7
Comments
Hi! This change was introduced in #3 and it is not configurable at this time. I'm going to add a config option to disable it. |
😳 so sorry, thought I searched issues and PRs! Awesome, thanks so much! |
@batpigandme, please use |
Awesome! Thanks so much 😊 |
batpigandme
added a commit
to batpigandme/ggplot2
that referenced
this issue
Jun 25, 2018
* Fixes tidyverse#2713 * Stop lockbot from marking issues as resolved. * See dessant/lock-threads#7 re. new `setLockReason` param. * Add lockComment explaining why issue locked.
hadley
pushed a commit
to tidyverse/ggplot2
that referenced
this issue
Jul 8, 2018
* Update lockbot reason 🔒🤖 * Fixes #2713 * Stop lockbot from marking issues as resolved. * See dessant/lock-threads#7 re. new `setLockReason` param. * Add lockComment explaining why issue locked. * Add reprex link
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
Love your probots!
It was just pointed out that the lock bot is locking threads "as resolved" (e.g. see here).
Is there a way to reconfigure so it's locking without a reason, as in the example (and as I modified, above)? The
lock.yml
for that repo is here. I don't think I've configured it specifically for "resolved" anywhere, but could easily be missing something.Thanks for your help.
Mara
The text was updated successfully, but these errors were encountered: