tag detection and gcs upload

[aslam-quad]

tag detection and gcs upload

Submission Checklist

NOTE: Community submissions can take up to 2 weeks to be reviewed.

Please take the following actions before submitting this pull request.

• Fork your PR branch from the Toolkit "develop" branch (not main)
• Test all changes with pre-commit in a local branch #
• Confirm that "make tests" passes all tests
• Add or modify unit tests to cover code changes
• Ensure that unit test coverage remains above 80%
• Update all applicable documentation
• Follow Cluster Toolkit Contribution guidelines #

[gemini-code-assist]

Summary of Changes

Hello @aslam-quad, 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 introduces a new automation script designed to streamline the release publishing workflow. By automatically identifying the latest Git tag and uploading a structured manifest to Google Cloud Storage, it enhances the efficiency and reliability of communicating new software releases.

Highlights

• New Release Publishing Script: A new bash script, tools/publish_release.sh, has been added to automate the process of detecting the latest Git tag and publishing release information.
• Automated Tag Detection: The script automatically fetches the latest Git tag from the repository and uses it as the release name and tag in the manifest.
• GCS Manifest Upload: It generates a JSON manifest containing release details and uploads it to a predefined Google Cloud Storage (GCS) bucket, facilitating external release tracking.

Changelog

• tools/publish_release.sh
  • Added a new bash script to automate the detection of the latest Git tag and the upload of a release manifest to GCS.

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 introduces a new script, tools/publish_release.sh, to automate the creation and upload of a release manifest to GCS. The script correctly identifies the latest git tag for the release. My review focuses on improving the script's robustness and adherence to shell scripting best practices. I've suggested changes to handle command-line arguments as documented in the script's comments, which makes it more flexible. I've also recommended redirecting all error messages to stderr for better error handling and logging.