Repository navigation
ci: remove stale workflow - #3297
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: npmx-dev/npmx.dev/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 6 remain after this review. 📝 SummarySummary by CodeRabbit
WalkthroughThe scheduled and manually triggered stale-management workflow was deleted. Its issue and pull request jobs, permissions, stale thresholds, labels and operation limits were removed. ChangesStale management
Priority: ⬇️ Low Merge Risk: ⚪ Minimal · up to Automatic stale labeling and closure will stop as intended. No merge-blocking issue is identified; deleting existing stale labels remains a separate follow-up. 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Let's maybe hold off on deleting the stale-to-close label so that auto-closed issues can still be identified. I alone have a list of 9 auto-close notifications in my inbox of issues I was following, and the only reason I didn't bump them was because of the noise. Also, why don't we start by simply disabling the workflow? |
danielroe
left a comment
There was a problem hiding this comment.
thank you! ❤️
let's leave the labels for now
as far as disabling it, I prefer to remove the workflow so the status isn't hidden in the ui
🔗 Linked issue
🧭 Context
This PR removes the
stale.ymlworkflow.📚 Description
As suggested and agreed on Discord, this PR removes the stale action since it is mostly annoying us because we reopen most of the auto-closed PRs and issues. It was helpful when we had huge amounts of PRs in the beginning, but not necessary anymore.
Note
After merging, I think we can also delete the GitHub labels
staleandstale-to-closeitself as well. They will be removed from all PRs and issues that currently have them assigned, which is desired because they don't do much more, but they will be preserved in the history (timeline) of existing PRs so traceability is still guaranteed.