Add check_rank automation for Enterprise Contract #43
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
Introduces a config file for EC. The main motivation is to include the check_rank automation as suggested by KONFLUX-2392. I'm not confident that we want the other available checks, (for example we do have stories without epics, and epics without parent features, and we do choose our own priority for bugs and stories when grooming), so I'm just adding the `check_rank` option to begin with. However we don't do much ranking currently, so I think it's safe to try letting the automation do some ranking for us. (See config/template.yaml for the other automations available.) Ref: https://issues.redhat.com/browse/EC-578 Ref: https://issues.redhat.com/browse/KONFLUX-2392
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.
Introduces a config file for EC. The main motivation is to include the check_rank automation as suggested by KONFLUX-2392.
I'm not confident that we want the other available checks, (for example we do have stories without epics, and epics without parent features, and we do choose our own priority for bugs and stories when grooming), so I'm just adding the
check_rankoption to begin with.However we don't do much ranking currently, so I think it's safe to try letting the automation do some ranking for us.
(See config/template.yaml for the other automations available.)
Ref: EC-578, KONFLUX-2392