Skip to content
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

chore(stale action): close stale issues as not planned #16610

Merged
merged 1 commit into from
Jul 16, 2022

Conversation

HonkingGoose
Copy link
Collaborator

Changes

  • Stale bot now closes stale issues with the reason "not-planned"

Context

GitHub recently released "issue closed reasons". When closing an issue you can choose to:

  • Close as completed (Done, closed, fixed, resolved)
  • Close as not planned (Won't fix, can't repro, duplicate, stale)

With actions/stale v5.1.0 you can now set the close-issue-reason.

I think the stale action should always close issues as "Close as not planned", because we need the reproduction to work on the issue.

References

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please tick one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

@rarkins rarkins enabled auto-merge (squash) July 16, 2022 06:38
@rarkins rarkins merged commit b1dd241 into renovatebot:main Jul 16, 2022
@HonkingGoose HonkingGoose deleted the patch-5 branch July 16, 2022 06:42
@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 32.117.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants