ci: cleanup release-please config after 1.0.0a0#854
Conversation
Remove draft and last-release-sha.
Summary of ChangesHello, 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 streamlines the release-please configuration by removing temporary settings that are no longer needed after the initial alpha release. This ensures the configuration accurately reflects the current state of the release process and avoids potential conflicts or confusion in future releases. Highlights
Changelog
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request cleans up the release-please-config.json file by removing the last-release-sha and draft properties. This is a standard procedure after an initial release has been created. The changes are correct and align with the goal of tidying up the release configuration.
🧪 Code Coverage (vs
|
Remove draft and last-release-sha.