Skip to content

Support the "not planned" state reason (when available) #744

@spenserblack

Description

@spenserblack

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions