Feature Request: always exclude Issues that are "Closed as not planned" aka: state_reason: not_planned

[vordimous]

Describe the bug
Closing issues with reason:"not planned" shouldn't be included or should be under a different section.

[olleolleolle]

There is a Label-based setting --exclude-labels.

Its default is:

exclude-labels=duplicate,question,invalid,wontfix,weekly-digest,dependencies

Are you referring to a Label?

[vordimous]

I mean, when I close issues as not planned:

There isn't a label assigned that I know of and the default exclusion rules seem to line up with the flavor text under the Close as un planned option. GitHub adds a reason: "not planned" attribute to the issue.

[olleolleolle]

This feature was added in May 2022, and can be read about in this release announcement https://github.blog/changelog/2022-05-19-the-new-github-issues-may-19th-update/

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.

Some of the REST docs currently say: https://docs.github.com/en/rest/issues/issues?apiVersion=2022-11-28#get-an-issue

state_reason: string or null

The reason for the state change. Ignored unless state is changed.

Can be one of: completed, not_planned, reopened, null.

I think a sensible default would be "always exclude state_reason: "not_planned".

Let's mark this Issue a feature request.