ci: 👷‍♂️ fix up stale issue handler

[lloydrichards]

Goals/Scope

There have been issues (#6417) and discussions (#1374) on the topic of maintainers and general entropy within the Issues and Pull Requests. While looking into what automation can be done for this I noticed you already had an Stale Issue workflow on hand, but it doesn't seem to be working.

Looking at the Issue Stale Action it seems that the PAT isn't correctly configured and for some reason the action returns a pass (false positive). While fixing the issue should only require some repository changes I thought I would also align the workflow with the current version from vercel/nextjs as there have been updates.

Description

For the action, I've mostly broken up the implementations for the Issue and PR handeling so there are more focused degrees of concern.

• issue-stale should only deal with Issues and mark them as stale after 30 days and close after a week.
• pr-stale should only deal with PRs and mark them as stale after 3 months and close after a week

These values can be tweaked depending on your desired retention, but seem reasonable for now.

How to Test

There is a way to run the workflow in dry-run mode, which might be useful for sorting out the CI incase of errors

Comments

@shadcn In order to fix the credential issue with the action you will need to add a PAT to the secrets under the name STALE_TOKEN. See Recommended Permission for the scope:

permissions:
  contents: write # only for delete-branch option
  issues: write
  pull-requests: write

---

• Urgent!

[vercel]

@lloydrichards is attempting to deploy a commit to the shadcn-pro Team on Vercel.

A member of the Team first needs to authorize it.