Add workflow to tag low priority items #4425
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
champnic
requested changes
Mar 26, 2024
Co-authored-by: Nic Champagne Williamson [MSFT] <[email protected]>
champnic
approved these changes
Mar 26, 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.
Part of the effort to be communicate to our 3P partners about work status. We would want to update users about lower priority items that will be unlikely to be addressed in the near future.
This workflow, currently a manually dispatched process, looks at our ADO query, and tags those items as low priority accordingly. We could eventually make this become a scheduled process.
This utilizes the following actions / libraries:
Simultaneously, I have added the following information to the readme to describe what the tags mean:
