Mention that the [lock] hander is enabled org-wide#1058
Conversation
| > [!NOTE] | ||
| > This feature is [enabled by default](https://github.com/rust-lang/triagebot/blob/master/rust-lang.triagebot.toml) in the rust-lang organization. | ||
|
|
||
| This feature is enabled on a repository by having a `[lock]` table in `triagebot.toml`: |
There was a problem hiding this comment.
Hmm I'm slightly confused, I feel these two sentences are now contradicting each other but maybe I am missing something.
What does rust-lang/triagebot@a4fd51b actually do? Do individual repositories need to enable the flag with [lock] in their triagebot.toml or is now the feature already enabled by default in the whole GH rust-lang (i.e. it's an opt-out flag)? If the flag is opt-out, maybe we should document how to add exception.
There was a problem hiding this comment.
It's the same message added to all the org-wide enabled handlers (see #1045).
What does rust-lang/triagebot@a4fd51b actually do?
It enables the [lock] handler for the repositories that have a triagebot.toml without having them to manually add it to their triagebot.toml.
maybe we should document how to add exception
The opt-out mechanism is described in the rust-lang.triagebot.toml.
There was a problem hiding this comment.
Hmm I'm slightly confused, I feel these two sentences are now contradicting each other but maybe there I am missing something.
I don't think they contradict each other.
The first one informs that it's enabled org-wide, the rest is normal description on how to enable it manually, which is particularly useful for handlers that have options (not this one).
rust-lang/triagebot#2420
r? @apiraino
Rendered