Skip to content

Conversation

@cgwalters
Copy link
Contributor

@cgwalters cgwalters commented Jan 22, 2026

Add a custom regex manager to track git commit SHAs in GitHub Actions workflow files. The pattern matches:

  # renovate: datasource=git-refs depName=https://github.com/org/repo branch=main
  VAR: '1234abcd...'

This enables renovate to automatically update pinned commit references when the tracked branch (e.g., main) advances.

Assisted-by: Claude Sonnet 4 (via OpenCode)

@gemini-code-assist
Copy link

Summary of Changes

Hello @cgwalters, 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 enhances our Renovate configuration by integrating a new custom manager. This addition enables the automated tracking and updating of Git commit SHAs within GitHub Actions workflow files, ensuring that pinned references remain current with the latest commits on specified branches. This improves the maintainability and security of our CI/CD pipelines by reducing manual updates and ensuring dependencies are up-to-date.

Highlights

  • New Renovate Custom Manager: Introduced a git-refs custom regex manager to Renovate's shared configuration. This manager is specifically designed to track and automatically update Git commit SHAs embedded within GitHub Actions workflow files.
  • Automated Commit SHA Tracking: The new manager enables Renovate to identify and update pinned commit references (e.g., VAR: '1234abcd...') in .yml and .yaml files. It uses a specific comment format (# renovate: datasource=git-refs depName=https://github.com/org/repo branch=main) to ensure these references stay current with the latest commits on a specified branch.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

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 adds a new custom regex manager to Renovate for tracking Git commit SHAs in GitHub Actions workflows. The implementation is a good start, but the regular expression could be made more robust to handle variations in formatting and to prevent potential parsing failures. I've left a specific suggestion to improve the regex.

@cgwalters cgwalters force-pushed the renovate-git-refs branch 2 times, most recently from d92ee9a to 5eaa40e Compare January 22, 2026 23:44
@gursewak1997
Copy link
Contributor

gursewak1997 commented Jan 23, 2026

Wait, isn't this already merged? This PR appears to have been rebased incorrectly. The commit (5eaa40e) now contains the minimumReleaseAge changes from #90, which is already merged as 06b397d. The original git-refs custom manager changes mentioned in the title/description have been lost.

Copy link
Contributor

@gursewak1997 gursewak1997 left a comment

Choose a reason for hiding this comment

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

Looks like wrong commit in here.

Add a custom regex manager to track git commit SHAs in Justfiles and
YAML workflows. The pattern matches both double-quoted (Justfile) and
single-quoted (YAML) strings containing 40-character commit SHAs.

Example usage:
  # renovate: datasource=git-refs depName=https://github.com/org/repo branch=main
  export VAR := env("VAR", "<40-char-sha>")  # Justfile
  VAR: '<40-char-sha>'                          # YAML

This enables Renovate to automatically update pinned commit references
when the tracked branch advances.

Assisted-by: OpenCode (Claude Sonnet 4)
@cgwalters cgwalters enabled auto-merge (squash) January 23, 2026 02:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants