Skip to content

Feat: Creating Bump Tag Action#8

Merged
JuanOioli merged 4 commits intomainfrom
feat/tag-release
Jun 30, 2025
Merged

Feat: Creating Bump Tag Action#8
JuanOioli merged 4 commits intomainfrom
feat/tag-release

Conversation

@JuanOioli
Copy link

  • Creating new action to Bumb Tag on Deployment

@JuanOioli JuanOioli requested a review from a team June 30, 2025 12:41
@JuanOioli JuanOioli self-assigned this Jun 30, 2025
@JuanOioli JuanOioli added the enhancement New feature or request label Jun 30, 2025
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @JuanOioli, 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 creates a new GitHub Action that automates the process of bumping the repository tag. It includes a Dockerfile to define the action's environment, a shell script (action.sh) containing the core logic for determining the next version, and an action.yml file to configure the action's inputs and outputs. This action simplifies release management by automatically updating the tag based on commit messages and predefined rules.

Highlights

  • New Action: This PR introduces a new GitHub Action to automatically bump the tag of a repository on deployment.
  • Dockerfile: A Dockerfile is added to define the environment for the action, including Node.js, git, and other utilities.
  • Action Script: The core logic for bumping the tag is implemented in action.sh, which determines the next version based on commit messages and configuration.
  • Action Configuration: The action.yml file defines the inputs and outputs of the action, making it reusable in GitHub workflows.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new GitHub Action for automatically bumping semantic version tags. The implementation is well-structured, but there are several areas for improvement. I've identified a potential bug in the tag-matching regex, suggested a more reliable method for default branch detection, and recommended using bash parameter expansion for safer string manipulation. Additionally, adding the inputs section to action.yml will greatly improve the action's usability.

@JuanOioli JuanOioli merged commit fe44d03 into main Jun 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants