fix(options)!: Make not_planned the default close-issue-reason#807
Merged
luketomlinson merged 2 commits intoactions:mainfrom Sep 20, 2022
Merged
fix(options)!: Make not_planned the default close-issue-reason#807luketomlinson merged 2 commits intoactions:mainfrom
not_planned the default close-issue-reason#807luketomlinson merged 2 commits intoactions:mainfrom
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Changes
close-issue-reasondefaults tonot_planned(previously: ``which defaulted to
completed) This closes the issue as 'not planned' on GitHub rather than 'completed'Context
GitHub introduced an additional close reason 'Close as not planned':
https://github.blog/changelog/2022-05-19-the-new-github-issues-may-19th-update/
'stale' is a use case for this close reason and makes sense as a default for this action
Fixes #789
Feature added: 06d2a39
Updated: aaab997