Modify/release workflow

[hoptical]

Summary by CodeRabbit

• Refactor
  • Updated the GitHub Actions workflow to enhance the build and release process.
• Chores
  • Changed the Helm chart repository path for pushing updates.
  • Added a new environment variable for improved authentication during releases.

[coderabbitai]

Walkthrough

The GitHub Actions workflow has been updated to include a new step for checking out the code, a change in the Helm chart repository destination, and the addition of an environment variable for authentication. These changes streamline the build and release process, ensuring the code is fetched properly, the Helm chart is pushed to the correct location, and secure access is maintained during the release.

Changes

File Path	Change Summary
.github/workflows/build-release.yaml	Added actions/checkout@v3 step, changed Helm chart repository, added GH_TOKEN environment variable

🐇✨
Changes in the flow, we hop and we go,
To fetch, to build, to release, we grow.
With tokens and charts, we set sail,
In the sea of code, we prevail. 🚀🌟

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• If you reply to a review comment from CodeRabbit, the bot will automatically respond.
• To engage with CodeRabbit bot directly around the specific lines of code in the PR, mention @coderabbitai in your review comment
• Note: Review comments are made on code diffs or files, not on the PR overview.
• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

Note: For conversation with the bot, please use the review comments on code diffs or files.

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

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 152882e and e3ed6bc.

Files selected for processing (1)

• .github/workflows/build-release.yaml (3 hunks)

Additional comments: 3

.github/workflows/build-release.yaml (3)

• 40-46: The addition of the OPERATOR_SDK_VERSION environment variable and the installation of operator-sdk are not mentioned in the summary. This change is significant as it introduces a specific version of a tool into the workflow, which could affect the build process.

• 58-71: The summary correctly identifies the change in the Helm chart repository destination. This change will affect where the Helm charts are stored and could impact any deployment processes or users that rely on pulling charts from the old location.

• 76-83: The addition of the GH_TOKEN environment variable in the release job is correctly noted in the summary. This token is likely used for authentication with GitHub to create releases, which is a critical part of the release process.