Compensation bot update - handle the nobot label #252
Merged
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
added 2 commits
October 23, 2021 10:01
… announcement sticky parsing
|
Nice! Thanks, @jmacxx |
|
I'm not sure how I can test this myself, but I assume @jmacxx has already done necessary diligence. EDIT: will merge as soon as @MwithM confirms the |
|
Apparently, it works. bisq-network/compensation#922 |
ghost
mentioned this pull request
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.
Per request by @cbeams the bot will check for the label
nobotand if found the issue is not parsed as a compensation request. If an issue has thenobotlabel applied after parsing, any existing bot-applied labels will be removed.Example from my test repo:
@MwithM please could you define the label
nobotin the https://github.com/bisq-network/compensation/labels.