chore(root): add develop branch to release workflow

[jrgarciadev]

Closes #

📝 Description

Add a brief description

⛳️ Current behavior (updates)

Please describe the current behavior that you are modifying

🚀 New behavior

Please describe the behavior or changes this PR adds

💣 Is this a breaking change (Yes/No):

📝 Additional Information

Summary by CodeRabbit

• Chores
  • Expanded workflow triggers to include the develop branch for enhanced development process flexibility.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9d88968

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nextui-docs-v2	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 10, 2024 2:11pm
nextui-storybook-v2	🔄 Building (Inspect)	Visit Preview		Mar 10, 2024 2:11pm

[coderabbitai]

Walkthrough

This update introduces a workflow modification where the develop branch, alongside the main branch, will now trigger workflow runs. This enhancement aims to streamline development and testing processes by allowing actions to execute in both primary branches, ensuring that changes in develop are as stable as those in main before merging.

Changes

File Path	Change Summary
.github/workflows/release.yaml	Added the develop branch to trigger workflow runs in addition to the main branch.

" left unfilled. This suggests that the PR may have been initiated without a corresponding issue or that the submitter forgot to link the relevant issue. The description sections intended to provide more context about the current behavior, new behavior, and whether the change is a breaking one are left with prompts for information rather than actual descriptions. This lack of detail means that the rationale, expected impact, and potential migration paths for existing users are not clearly communicated within the PR description.

Despite the sparse description, the core objective of the PR is clear: to update the .github/workflows/release.yaml file to include the develop branch in the release workflow triggers. This change is presumably aimed at improving the development and release process by allowing actions that were previously restricted to the main branch to also be performed from the develop branch, potentially facilitating a more flexible or staged approach to integration and deployment.

AI-generated Summary of Generated Summaries

The pull request introduces a modification to the project's GitHub Actions workflow configuration, specifically within the .github/workflows/release.yaml file. The key change involves adding the develop branch to the list of branches that can trigger the release workflow. Previously, only the main branch was configured to initiate workflow runs. By including the develop branch, the project aims to enhance its development and release process, allowing for a more dynamic and possibly staged approach to testing, integration, and deployment. This change is targeted at improving workflow efficiency and flexibility without altering the core functionality or introducing new features.

-->

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-tests 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 tests 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 tests.
  • @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.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: .coderabbit.yaml

Commits

Files that changed from the base of the PR and between 5a8768a and 9d88968.

Files selected for processing (1)

• .github/workflows/release.yaml (1 hunks)

Files skipped from review due to trivial changes (1)

• .github/workflows/release.yaml