feat(ci): Added github actions to publish helm chart

[Haferbeck-IT]

Hi,
github actions template and README as promised. Unfortunately im a gitlab ci user. Therefore I cannot verify the actions on my own. You will need to put a little bit of work in it.

Feel free to ask me if you need any help.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly improves the project's deployment experience by adding continuous integration for its Helm chart and enhancing the main documentation. It establishes a basic CI/CD pipeline for publishing the Helm chart and provides clear, concise instructions for users to quickly deploy the application on Kubernetes.

Highlights

• CI/CD for Helm Chart Publishing: Introduced GitHub Actions workflows to automate the publishing of the Helm chart, providing a foundational CI/CD pipeline.
• Documentation Update: Updated the README.md file to include a new "Quick Start (Kubernetes)" section with detailed instructions for deploying the application using Helm.

Changelog

• README.md
  • Added a new "Quick Start (Kubernetes)" section.
  • Included commands for installing the Helm chart via OCI registry and directly from source.
  • Provided guidance on customizing Helm values.
  • Referenced the dedicated Helm chart README for comprehensive configuration options.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/helm-release.yml

Activity

• The author, Haferbeck-IT, provided a GitHub Actions template for publishing the Helm chart.
• The author noted their unfamiliarity with GitHub Actions, being a GitLab CI user, and stated they could not verify the actions themselves.
• The author indicated that further work and verification would be needed to finalize and test the CI pipeline.
• The author offered assistance if any help was required.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds a "Quick Start (Kubernetes)" section to the main README.md file with instructions on how to deploy the application using the new Helm chart.

The instructions are a good starting point, but I've found a potential issue in the Helm commands provided for customizing an installation. The helm install command is used where helm upgrade would be appropriate, which could lead to errors for users following the steps sequentially. I've left a specific comment with a suggested fix to improve the clarity and correctness of the documentation.

Note that the GitHub Actions mentioned in the PR title and description do not appear to be included in the file changes for this pull request.

[gemini-code-assist]

The helm install command in step 2 will cause an error if you've already installed the chart in step 1, as a release named sparkyfitness will already exist. To modify an existing installation, you should use helm upgrade.

Additionally, this step requires the chart's source files, which is only guaranteed if installing from source. The suggested change clarifies this and uses the correct command.

Suggested change

	# 2. (Optional) Customize values
	helm install sparkyfitness ./SparkyFitness/helm/chart -f my-values.yaml
	# 2. (Optional) Upgrade with custom values (requires local chart source)
	helm upgrade sparkyfitness ./SparkyFitness/helm/chart -f my-values.yaml