ci/close-issues: support more issue ref notations #1599
Merged
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.
Closes #1592
What has been done to verify that this works as intended?
masterin the fork, and tested with various new issues and different structures of commit message. REVIEW: is this necessary?Why is this the best possible solution? Were any other approaches considered?
Another approach would be to extract the JS of the
scriptsection ofclose-issues.ymlinto a.jsfile, and write more traditional tests. However, this would be a much more significant change to the overhead of the workflow, asactions/checkoutwould have to be added, and NodeJS would need to be installed.How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
No effect.
Does this change require updates to documentation? If so, please file an issue here and include the link below.
No.
Before submitting this PR, please make sure you have:
nextbranch OR only changed documentation/infrastructure (masteris stable and used in production)