Fix 'Mark issues stale after needs testing for 30 days' workflow #43545
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
Mamaduka
added
the
[Type] Project Management
gziolo
approved these changes
Aug 24, 2022
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.
What?
PR fixes 'Mark issues stale after needs testing for 30 days' workflow by adding
stale-issue-message.Why?
I noticed that this workflow wasn't labeling the issues. After checking the logs and the
actions/stale, it looks like the stale message is required even when skipping the commenting on the issue.How?
I added the stale issue message — a modified version of the "no activity" workflow.
Testing Instructions
Not an easy one to test since it uses GitHub workflow. Best to review logic in the
actions/stale:skip-stale-issue-message- https://github.com/actions/stale/blob/v3.0.17/src/classes/issues-processor.ts#L451-L462