Closing issue as "not planned" instead of "completed" #24
Unanswered
browniebroke
asked this question in
Questions
Replies: 1 comment
-
Looks like this is supported in the latest version of PyGitHub by passing I guess it's a matter of changing this line: Line 101 in 0ec1d5a |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
First Check
Commit to Help
Example Code
Description
I used this GitHub action on one of the repos I maintain, and it worked great for me. Today, I used it to close an old issue, and I noticed that the issue was closed as "completed" while I was expecting it to be closed as "not planned", which sounds like a better default for this project. Is that something which is already supported?
I think that was added fairly recently to GitHub so maybe the API call made by the GitHub action needs a bit of tweaking. Perhaps it would make sense to have an option to make it configurable per label.
PS: I use this GitHub action on several of my repos, this is really helping me to stay on top of things, so thank you!
Operating System
Linux
Operating System Details
ubuntu-latest
Python Version
n/a
Additional Context
No response
Beta Was this translation helpful? Give feedback.
All reactions