chore: add a bot comment whenever the "request-discuss" label is added to a GH issue #18390
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…d to a GH issue The comment will be removed if the label is removed.
andresrc
approved these changes
May 8, 2020
|
Merging before CI finishes, as this PR relates to github bots configuration |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR adds the configuration for botelastic to support commenting whenever the
request-discusslabel is added to a GH issue.The comment will be removed if the label
request-discussis removed.Besides that, it fixes the name of the descriptor on one of the installed bot (probot-add-comment), which contained a typo on its name.
Why is it important?
In order to simplify the current triage process we would like to have a bot in the beats repository that performs the following operation:
Checklist
- [ ] My code follows the style guidelines of this project- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature works- [ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
How to test this PR locally
It's possible to test this configuration locally using probot's infrastructure provided by Infra team, but it could be out of the scope of this PR.
Related issues