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

issue1064 stale check #18

Merged
merged 1 commit into from
May 21, 2024
Merged

issue1064 stale check #18

merged 1 commit into from
May 21, 2024

Conversation

aceppaluni
Copy link
Member

The Pull Request is ready

  • fixes #issue1064
  • all actions are passing
  • only fixes a single issue

Overview

Add a stale check for framework

Review points

Added a new yml file to accommodate stale check
File placed in workflows

Framework

  • the change breaks no interface
  • default behaviour did not change
  • any new text output is added to the translation files (at least the english one)
  • tests have been added (if required)
  • documentation has been adjusted (if required)
  • shared code has been extracted in a different file

Notes

Issue associated with issue#1064

Copy link
Contributor

coderabbitai bot commented May 20, 2024

Walkthrough

The new workflow cron.stale.yml automates the management of stale issues and pull requests in the repository. It schedules jobs to close inactive issues and pull requests, unassign inactive contributors, and notify relevant parties. This ensures the repository remains up-to-date and contributors are informed about inactivity.

Changes

Files Change Summary
.github/workflows/cron.stale.yml Introduced a GitHub Actions workflow to handle stale issues and pull requests, and manage inactivity.

In the code's embrace, we find our way,

Stale issues now kept at bay.

Notifications sent with care,

Contributors aware, no despair.

Automation's touch, a gentle sway,

Keeping chaos far away.


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:

Note: Auto-reply has been disabled for this repository by the repository owner. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

  • 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.

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 a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

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

CodeRabbit Configration 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.

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 476d53f and 3910074.
Files selected for processing (1)
  • .github/workflows/cron.stale.yml (1 hunks)
Additional comments not posted (3)
.github/workflows/cron.stale.yml (3)

12-20: The configuration for the stale job appears to be well-defined and aligns with the objectives of managing stale issues and pull requests efficiently.


22-27: The configuration for the remove-assignee job is appropriate and aligns with the objectives of unassigning inactive contributors.


4-4: Consider adjusting the cron schedule to a less frequent interval unless high frequency is required.

@Idrinth Idrinth marked this pull request as ready for review May 21, 2024 04:05
@Idrinth Idrinth merged commit 53950f0 into the-one May 21, 2024
3 of 5 checks passed
@Idrinth Idrinth deleted the jul-contribute branch May 21, 2024 04:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants