TEST_NEW_LABELER: dont merge #2
Open
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
github-actions
bot
added
documentation
KKoukiou
force-pushed
the
master
branch
26 times, most recently
from
098d80c to
126f63a
Compare
KKoukiou
force-pushed
the
master
branch
3 times, most recently
from
200a3e8 to
16b9633
Compare
KKoukiou
force-pushed
the
master
branch
6 times, most recently
from
273c0af to
d6e326d
Compare
KKoukiou
force-pushed
the
master
branch
6 times, most recently
from
8019d68 to
ccea668
Compare
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.
Thank you for your contribution!
Please check that your PR follows these rules:
Code conventions. tl;dr: Follow PEP8, wrap at 100 chars, and provide docstrings.
Commit message conventions. tl;dr: Heading, empty line, longer explanations, all wrapped manually. If in doubt, write a longer commit message with more details.
Tests pass and cover your changes. You can run tests locally manually, or have them run as part of the PR. A team member will have to enable tests manually after inspecting the PR.
If you don't know how, ask us for help!
Release notes and docs if the PR adds something major or changes existing behavior.
If you don't know how, ask us for help!
RHEL rules: If your PR is for a
rhel-*branch, pay special attention to commit messages. Make sure all commit messages include a line linking the commit to a bug, such asResolves: rhbz#123456. For more information, see the complete rules.If you don't know how, ask us for help!
Don't forget - if you don't know how, ask us for help!
And now that you read this all, you can delete it and type your own description of your changes :-)