FabricMC/fabric-action-scripts

Close support issues as not planned

Closed this issue · 1 comments

Although the GitHub REST API does not document any way of differentiating closed issues between completed and not planned, it seems that a state_reason value of not_planned would allow the workflow to close the issue as not planned:

gh api -X PATCH repos/FabricMC/fabric-action-scripts/issues/7 -f state='closed' -f state_reason='not_planned'

Seems it should be that easy 👍