Skip to content

Move the GoReleaser config to the root#292

Merged
5ouma merged 3 commits intomainfrom
ci-goreleaser-path
Apr 22, 2025
Merged

Move the GoReleaser config to the root#292
5ouma merged 3 commits intomainfrom
ci-goreleaser-path

Conversation

@5ouma
Copy link
Owner

@5ouma 5ouma commented Apr 22, 2025

⚠️ Issue

close #


✏️ Description

Its config is not only for GitHub.

@5ouma
ci(goreleaser): Move the config to the root
a19c285 
Its config is not only for GitHub.
Copilot AI review requested due to automatic review settings April 22, 2025 06:04
@coderabbitai
Copy link

coderabbitai bot commented Apr 22, 2025 •
edited
Loading

Walkthrough

The GitHub Actions workflow for releases was updated by changing the GoReleaser invocation. The explicit configuration file argument (--config=.github/goreleaser.yml) was removed from the command, simplifying it to use the default configuration. No other modifications were made to the workflow file or to any exported or public entities.

Changes

File(s) Change Summary
.github/workflows/release.yml Removed the --config=.github/goreleaser.yml argument from the GoReleaser action command.
📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8c81151 and 5b997ca.

📒 Files selected for processing (1)
  • .github/workflows/release.yml (1 hunks)
🔇 Additional comments (1)
.github/workflows/release.yml (1)

71-71: Verify relocation and naming of the GoReleaser config file
Since you removed the explicit --config=.github/goreleaser.yml flag, GoReleaser will now default to looking for its configuration at the repository root (e.g. goreleaser.yml or .goreleaser.yml). Please confirm that the config file has indeed been moved to the root and is named correctly; otherwise, the release step will fail due to a missing config.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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 generate docstrings to generate docstrings for this 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.

@github-actions github-actions bot added the 🎽 CI Changes to CI configuration files and scripts label Apr 22, 2025
Copilot AI reviewed Apr 22, 2025
View reviewed changes
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR moves the GoReleaser configuration file from the .github directory to the project root, simplifying the release command.

  • Removed the explicit --config flag from the release command.
  • Updated the workflow to rely on GoReleaser's default behavior for locating the config file.
Comments suppressed due to low confidence (1)

.github/workflows/release.yml:64

  • Since the GoReleaser config has been moved to the root, removing the '--config' flag aligns with the update. Please verify that the release process consistently locates the correct configuration in all environments.
args: release --clean

@5ouma
Copy link
Owner Author

5ouma commented Apr 22, 2025

@coderabbitai review

@5ouma 5ouma merged commit 2aa480f into main Apr 22, 2025
5 of 6 checks passed
@5ouma 5ouma deleted the ci-goreleaser-path branch April 22, 2025 07:36
@github-actions github-actions bot mentioned this pull request Apr 22, 2025
Merged
This was referenced Dec 12, 2025
Merged
Merged
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments

@coderabbitai coderabbitai[bot] coderabbitai[bot] approved these changes

Assignees

@5ouma 5ouma

Labels

🎽 CI Changes to CI configuration files and scripts

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@5ouma