Update Zube worklow to move issues to "QA Review" for QA/dev-automation #9944
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
richard-cox
approved these changes
Nov 22, 2023
yonasberhe23
pushed a commit
to yonasberhe23/dashboard
that referenced
this pull request
Dec 20, 2023
yonasberhe23
pushed a commit
to yonasberhe23/dashboard
that referenced
this pull request
Jan 26, 2024
yonasberhe23
pushed a commit
to yonasberhe23/dashboard
that referenced
this pull request
Jan 29, 2024
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.
This PR updates our Zube workflow.
When a PR is merged, any linked issues will be moved to "QA Review" instead of "To Test" IF the issue has the "QA/dev-automation' label - which indicates that automated tests should have been written for the issue and that QA need to review that these tests are sufficient to test the feature, rather than "To Test', which indicates that QA need to manually test the issue.
Tested this manually on a test repository.