Visitar URL original
fix(options)!: Make `not_planned` the default `close-issue-reason` by david-allison · Pull Request #807 · actions/stale · GitHub
Skip to content

fix(options)!: Make not_planned the default close-issue-reason - #807

Merged
luketomlinson merged 2 commits into
actions:mainfrom
david-allison:fix-789
Sep 20, 2022
Merged

luketomlinson merged 2 commits into
actions:mainfrom
david-allison:fix-789

Conversation

@david-allison

@david-allison david-allison commented Sep 5, 2022 •

Copy link
Copy Markdown
Contributor

Changes

  • ⚠️ BREAKING CHANGE close-issue-reason defaults to not_planned (previously: ``
    which defaulted to completed) This closes the issue as 'not planned' on GitHub rather than 'completed'
  • documentation: minor improvement to 'DefaultProcessorOptions'
    • I'm happy to drop this if it's an issue - unsure on PR requirements for this repo

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

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

Fixes actions#789

BREAKING CHANGE:
`close-issue-reason` defaults to `not_planned` (previously: ``
which defaulted to `completed`)
This closes the issue as 'not planned' on GitHub rather than 'completed'

See: https://github.blog/changelog/2022-05-19-the-new-github-issues-may-19th-update
@david-allison

Copy link
Copy Markdown
Contributor Author

Fixed conflicts. Is anything required on my end to get this merged?

@jeffwidman jeffwidman left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems like the sane default.

I realize it's technically a breaking change so may require a v6, but I doubt many users have workflow that changes base on the close-issue-reason attribute so blast radius is probably pretty small... could also argue that the previous value was simply "unset" and this isn't so much a breaking change as simply a "enhancement" of setting the value...

@Ronaldbk Ronaldbk mentioned this pull request Sep 20, 2022
@luketomlinson
luketomlinson merged commit 02e44c8 into actions:main Sep 20, 2022
@david-allison
david-allison deleted the fix-789 branch September 20, 2022 18:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Make not_planned the default close-issue-reason

3 participants