Skip to content

chore: Do not mark User testing PRs as stale#35806

Merged
hetunandu merged 1 commit intoreleasefrom
fix/pr-stale-check
Aug 21, 2024
Merged

chore: Do not mark User testing PRs as stale#35806
hetunandu merged 1 commit intoreleasefrom
fix/pr-stale-check

Conversation

@hetunandu
Copy link
Member

@hetunandu hetunandu commented Aug 21, 2024

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

  • New Features
    • Added the User Testing label 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.

@hetunandu hetunandu requested a review from sharat87 as a code owner August 21, 2024 08:31
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 21, 2024

Walkthrough

The recent update enhances the GitHub stale workflow by adding the label User Testing to the list of exempt pull request labels. This modification allows pull requests under user testing to remain open despite periods of inactivity, promoting a more flexible review process. This change ensures that essential pull requests can undergo extended testing without the risk of being closed automatically, thereby improving collaboration and quality assurance in the development cycle.

Changes

Files Change Summary
.github/workflows/stale.yml Added User Testing to exempt-pr-labels, allowing pull requests labeled this way to avoid inactivity closure.

Poem

In the realm of code so bright,
Labels dance in the soft moonlight.
User Testing joins the rest,
Keeping pull requests at their best.
No more worries of a hasty close,
For every trial, a chance to pose! 🌟


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?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@hetunandu hetunandu requested review from a team and removed request for sharat87 August 21, 2024 08:32
@hetunandu hetunandu changed the title Update stale.yml chore: Do not mark User testing PRs as stale Aug 21, 2024
@github-actions github-actions bot added the skip-changelog Adding this label to a PR prevents it from being listed in the changelog label Aug 21, 2024
@hetunandu hetunandu added User Testing CI and removed skip-changelog Adding this label to a PR prevents it from being listed in the changelog labels Aug 21, 2024
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5268164 and f27d4ce.

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 Testing to the exempt-pr-labels, you ensure that PRs needing extended user testing are not prematurely closed. This change supports a more thorough testing process. Well done!

@github-actions github-actions bot added skip-changelog Adding this label to a PR prevents it from being listed in the changelog and removed CI labels Aug 21, 2024
@hetunandu hetunandu merged commit 3e38ae5 into release Aug 21, 2024
@hetunandu hetunandu deleted the fix/pr-stale-check branch August 21, 2024 08:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-changelog Adding this label to a PR prevents it from being listed in the changelog User Testing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants