This limits which actions the validate_config handler will handle. There was a problem where it was validating the config on every action. This means that if there is an invalid config, and any action was performed on the PR (like adding a label, or assigning someone), it would post a comment about the invalid config.
This is particularly a problem with old closed PRs that modified triagebot.toml. Minor actions like adding milestones or labels shouldn't re-trigger validation.
This limits which actions the validate_config handler will handle. There was a problem where it was validating the config on every action. This means that if there is an invalid config, and any action was performed on the PR (like adding a label, or assigning someone), it would post a comment about the invalid config.
This is particularly a problem with old closed PRs that modified
triagebot.toml. Minor actions like adding milestones or labels shouldn't re-trigger validation.Fixes https://github.com/rust-lang/triagebot/issues/1802