chore:automations

[JarbasAl]

Summary by CodeRabbit

• New Features

  • Introduced automated workflows for labeling pull requests and managing stable releases.
  • Implemented a release workflow that automates the publishing of alpha versions and notifications upon merges.

• Enhancements

  • Streamlined release management processes, reducing manual intervention and improving efficiency.

[coderabbitai]

Warning

Rate limit exceeded

@github-actions[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 0 minutes and 24 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 99f1f0f and 828fc0e.

Walkthrough

The changes introduce three new GitHub Actions workflows: conventional-release-labels, publish_stable, and release_workflow. These workflows automate the labeling of pull requests, manage the publishing of stable releases, and streamline the release process for alpha versions. They include jobs for publishing to Test PyPI, notifying team members, and proposing stable releases based on merged pull requests.

Changes

Files	Change Summary
.github/workflows/conventional-label.yml	Introduced a workflow for automatic labeling of PRs based on conventional practices.
.github/workflows/publish_stable.yml	Created a workflow to automate stable release publishing and synchronize the development branch.
.github/workflows/release_workflow.yml	Added a workflow for automating the release process, including alpha publishing and notifications.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GitHub
    participant Workflow
    participant PyPI
    participant Chat

    User->>GitHub: Open PR
    GitHub->>Workflow: Trigger on PR open
    Workflow->>GitHub: Add labels
    User->>GitHub: Merge PR
    GitHub->>Workflow: Trigger on PR merge
    Workflow->>PyPI: Publish alpha version
    Workflow->>Chat: Notify about merge
    Workflow->>GitHub: Propose stable release

Loading

🐇 In the garden, we hop and play,
New workflows bloom, brightening the day.
Labels and releases, all in a row,
With every merge, our project will grow!
Hooray for the changes, let’s give a cheer,
For smoother releases, we hold dear! 🌼✨

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.