chore(go-feature-flag): Remove release-as 1.0.0 in the release please config #1591
Conversation
… config Signed-off-by: Thomas Poignant <thomas.poignant@gofeatureflag.org>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Summary of Changes
Hello @thomaspoignant, I'm Gemini Code Assist1! 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 updates the release-please configuration by removing a hardcoded version override. The intent is to enable the automated release process to follow its default semantic versioning logic, ensuring that new releases are versioned dynamically based on commit history rather than being constrained to a specific initial version.
Highlights
- Release Configuration: The
release-as: "1.0.0"property has been removed from therelease-please-config.jsonfile. This change allows therelease-pleasetool to automatically determine the next version based on conventional commits, rather than being fixed at version 1.0.0.
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
-
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. ↩
There was a problem hiding this comment.
Code Review
This pull request removes the hardcoded release-as: "1.0.0" configuration for the go-feature-flag provider in the release-please-config.json file. This is a positive change that allows the release-please tool to automatically manage versioning based on commit history, which is standard practice after an initial release. The change is correct and improves the release automation process.
|
The previous release did not work. See #1592 |
4 participants
Remove release-as 1.0.0 in the release please config