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

ci: release on discord only stable versions #194

Merged
merged 1 commit into from
Nov 8, 2024

Conversation

fadeev
Copy link
Member

@fadeev fadeev commented Nov 8, 2024

Summary by CodeRabbit

  • Chores
    • Updated the GitHub Actions workflow to conditionally release to Discord based on the release tag naming convention, improving control over release processes.

@fadeev fadeev requested review from andresaiello and a team as code owners November 8, 2024 07:39
Copy link
Contributor

coderabbitai bot commented Nov 8, 2024

📝 Walkthrough

Walkthrough

The changes in this pull request modify the GitHub Actions workflow for releasing to Discord by introducing a conditional statement in the job github-releases-to-discord. This condition checks if the release tag name does not contain a hyphen (-). If the tag name includes a hyphen, the job will not execute, thereby altering the control flow based on the tag naming convention.

Changes

File Change Summary
.github/workflows/release-to-discord.yaml Added a conditional statement to the job github-releases-to-discord to check for hyphens in the release tag name.

Possibly related PRs

Suggested reviewers

  • andresaiello
  • GMaiolo

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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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.

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

🧹 Outside diff range and nitpick comments (1)
.github/workflows/release-to-discord.yaml (1)

7-7: Consider adding documentation about version filtering.

To improve maintainability, consider adding a comment explaining the version filtering logic and providing examples of which tags will/won't trigger Discord notifications.

 jobs:
   github-releases-to-discord:
+    # Only notify Discord for stable releases (e.g., v1.0.0)
+    # Pre-release versions with hyphens (e.g., v1.0.0-beta.1) are skipped
     if: "! contains(github.event.release.tag_name, '-')"
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between cbba6dd and 669a8c3.

📒 Files selected for processing (1)
  • .github/workflows/release-to-discord.yaml (1 hunks)
🔇 Additional comments (1)
.github/workflows/release-to-discord.yaml (1)

7-7: LGTM! Let's verify the condition works as expected.

The condition effectively filters out pre-release versions by checking for hyphens in the tag name, which aligns with semantic versioning conventions.

Let's verify the tag naming patterns in the repository:

✅ Verification successful

✅ Condition correctly filters pre-release versions

The release history confirms that the condition ! contains(github.event.release.tag_name, '-') will work as intended:

  • It will skip pre-release versions (v13.0.0-rc7, v13.0.0-rc6, etc.)
  • It will allow stable releases (v12.0.0, v11.0.0)

This perfectly aligns with the repository's versioning pattern where:

  • Stable releases use format: vX.Y.Z
  • Pre-releases use format: vX.Y.Z-rcN
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check existing tag patterns to ensure the condition matches the intended behavior

# Test: List all tags and their patterns
git tag | sort -V

# Test: Specifically check for any tags with hyphens that would be filtered
git tag | grep "-" || echo "No tags with hyphens found"

Length of output: 101


Script:

#!/bin/bash
# Let's check the release history to understand the version patterns
gh release list --limit 10

Length of output: 566

Copy link
Collaborator

@GMaiolo GMaiolo left a comment

Choose a reason for hiding this comment

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

utACK

@fadeev fadeev merged commit 78fa8d7 into main Nov 8, 2024
5 checks passed
@fadeev fadeev deleted the discord-release-only-stable branch November 8, 2024 18:17
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.

3 participants