[FEATURE] Allow to define the type of closing reason #779
Assignees
Labels
feature-request 🚀
Contains a feature/enhancement request
released 📦
Added when a Github/npm release was made
Comments
C0ZEN
added a commit
that referenced
this issue
Aug 23, 2022
…uest-close-reason` Those inputs allow you to specify the reason for closing an item. Closes #779 BREAKING CHANGE: The close reason will now be by default 'NOT_PLANNED' instead of 'COMPLETED' since it makes more sense. If you want to change the new default behavior, you can use these inputs: issue-close-reason: 'completed' pull-request-close-reason: 'completed'
C0ZEN
added a commit
that referenced
this issue
Aug 23, 2022
…uest-close-reason` Those inputs allow you to specify the reason for closing an item. Closes #779 BREAKING CHANGE: The close reason will now be by default 'NOT_PLANNED' instead of 'COMPLETED' since it makes more sense. If you want to change the new default behavior, you can use these inputs: issue-close-reason: 'completed' pull-request-close-reason: 'completed'
C0ZEN
added a commit
that referenced
this issue
Aug 23, 2022
…uest-close-reason` Those inputs allow you to specify the reason for closing an item. Closes #779 BREAKING CHANGE: The close reason will now be by default 'NOT_PLANNED' instead of 'COMPLETED' since it makes more sense. If you want to change the new default behavior, you can use these inputs: issue-close-reason: 'completed' pull-request-close-reason: 'completed'
C0ZEN
added a commit
that referenced
this issue
Aug 23, 2022
…uest-close-reason` Those inputs allow you to specify the reason for closing an item. Closes #779 BREAKING CHANGE: The close reason will now be by default 'NOT_PLANNED' instead of 'COMPLETED' since it makes more sense. If you want to change the new default behavior, you can use these inputs: issue-close-reason: 'completed' pull-request-close-reason: 'completed'
C0ZEN
added a commit
that referenced
this issue
Aug 23, 2022
…uest-close-reason` Those inputs allow you to specify the reason for closing an item. Closes #779 BREAKING CHANGE: The close reason will now be by default 'NOT_PLANNED' instead of 'COMPLETED' since it makes more sense. If you want to change the new default behavior, you can use these inputs: issue-close-reason: 'completed' pull-request-close-reason: 'completed'
16 tasks
C0ZEN
added a commit
that referenced
this issue
Aug 23, 2022
…uest-close-reason` Those inputs allow you to specify the reason for closing an item. Closes #779 BREAKING CHANGE: The close reason will now be by default 'NOT_PLANNED' instead of 'COMPLETED' since it makes more sense. If you want to change the new default behavior, you can use these inputs: issue-close-reason: 'completed' pull-request-close-reason: 'completed'
C0ZEN
added a commit
that referenced
this issue
Aug 23, 2022
…uest-close-reason` Those inputs allow you to specify the reason for closing an item. Closes #779 BREAKING CHANGE: The close reason will now be by default 'NOT_PLANNED' instead of 'COMPLETED' since it makes more sense. If you want to change the new default behavior, you can use these inputs: issue-close-reason: 'completed' pull-request-close-reason: 'completed'
|
🎉 This issue has been resolved in version 1.62.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sonia-corporation-bot
added
the
released 📦
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the solution you'd like
Allow to change the type of closing reason following https://github.blog/changelog/2022-05-19-the-new-github-issues-may-19th-update/
The text was updated successfully, but these errors were encountered: