Skip to content
This repository has been archived by the owner on May 20, 2023. It is now read-only.

New Github Issues: Close reasons #379

Open
real-yfprojects opened this issue May 31, 2022 · 3 comments · May be fixed by #382
Open

New Github Issues: Close reasons #379

real-yfprojects opened this issue May 31, 2022 · 3 comments · May be fixed by #382

Comments

@real-yfprojects
Copy link

The May 19th update of github introduced new issue functionality including two different kinds of close action that are differ by their reason attribute. This can be either complete or not-planned. Currently the stale bot closes issues as completed though the issue is very likely not to be completed and not-planned would be a better reason for closing stale issues.
@tjenkinson
Copy link

tjenkinson commented Aug 8, 2022 •
edited by unfurl-links bot
Loading

Looks like this isn't possible with the rest api yet https://docs.github.com/en/rest/issues/issues#update-an-issue

state string
State of the issue. Either open or closed.

GitHub Docs
Get started, troubleshoot, and make the most of GitHub. Documentation for new users, developers, administrators, and all of GitHub's products.

@tjenkinson
Copy link

tjenkinson commented Aug 8, 2022 •
edited by unfurl-links bot
Loading

ok so https://github.blog/changelog/2022-05-19-the-new-github-issues-may-19th-update/ says

We have added a new state_reason attribute to our REST API, GraphQL API and webhooks. These are currently in preview and will be fully shipped in the upcoming week.

But it looks the docs aren't updated given actions/stale#744 has been done and apparently works

tjenkinson added a commit to tjenkinson/stale that referenced this issue Aug 8, 2022
@tjenkinson
use not_planned close reason
f412bdc 
closes probot#379
@tjenkinson tjenkinson linked a pull request Aug 8, 2022 that will close this issue
Open
@tjenkinson
Copy link

Opened a PR here: #382

@tjenkinson tjenkinson mentioned this issue Aug 8, 2022
Closed
1 task
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

use not_planned close reason tjenkinson/stale
2 participants
@tjenkinson @real-yfprojects