Tagger workflow#9
Closed
ChrisLovering wants to merge 2 commits into
Closed
Conversation
ChrisLovering
force-pushed
the
tagger-workflow
branch
from
e2db6df to
b1db511
Compare
This will automatically apply any labels, as defined in the auto_tagger_config.yaml config file. This runs on PR open, reopen and syncronize, which is triggered when a commit is pushed to the PR branch. If the label doesn't exist in the repo, it will be created automatically.
ChrisLovering
force-pushed
the
tagger-workflow
branch
from
b1db511 to
276db5d
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This workflow will automatically apply any labels, as defined in the auto_tagger_config.yaml config file. This runs on PR open, reopen and synchronize, which is triggered when a commit is pushed to the PR branch.
If the label doesn't exist in the repo, it will be created automatically.
This allows us to enforce the removal of a "needs testing" tag before any PRs are merged, as reminder for us that PRs should be tested by at least one person before merging.