-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support the "not planned" state reason (when available) #744
Comments
I think this action should close stale issues as not planned by default, with an option to close as complete if desired. 🙂 The help text for close as not planned even mentions Perhaps an option like jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v4
with:
close-as-complete: true # default: false A more future-proof option might be something like jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v4
with:
state-reason: complete # default: not-planned |
Update
|
I see a way to do it via GraphQL (via a dedicated closeIssue mutation rather than updateIssue) but I don't see a way via REST API unless the documentation is not updated? |
I manually tested the REST API and found that passing |
Apologies if this duplicates anything, but I didn't see this mentioned in the README or any issues.
The problem
GitHub Issues can now have a state reason (why they were closed). Currently,
actions/stale
closes as complete, and it doesn't look like there is an input to change that behavior.I'm not sure if this has been released for the REST API yet, but it's at least planned. I'm wondering if, when it is available in the API, there are plans for this action to support it.
The solution
When it's available via the API, perhaps a
close-issue-reason
input, which defaults to "complete" to keep the current behavior, but also allows "not planned" input.The text was updated successfully, but these errors were encountered: