chore: Do not mark User testing PRs as stale#35806
Conversation
WalkthroughThe recent update enhances the GitHub stale workflow by adding the label Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Files selected for processing (1)
- .github/workflows/stale.yml (1 hunks)
Additional comments not posted (1)
.github/workflows/stale.yml (1)
27-27: Great addition to the exempt labels!By adding
User Testingto theexempt-pr-labels, you ensure that PRs needing extended user testing are not prematurely closed. This change supports a more thorough testing process. Well done!
Description
Adds a new exception on the stale check workflow. If the PR has the flag of "User Testing", it will not mark it as stale.
Warning
Tests have not run on the HEAD f27d4ce yet
Wed, 21 Aug 2024 08:34:31 UTC
Summary by CodeRabbit
User Testinglabel to the list of exempt labels, preventing pull requests in user testing from being closed due to inactivity. This enhances workflow management for extended reviews or testing periods.