Cleanup old branches.

[jacob314]

Summary

Cleanup stale branches

Fixes #19353

[gemini-code-assist]

Summary of Changes

Hello @jacob314, 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 utility script designed to maintain repository cleanliness by automatically identifying and offering to remove stale remote branches. The script streamlines the process of decluttering the branch list, focusing on branches that are inactive, unprotected, and not tied to any open pull requests, thereby improving repository hygiene and developer experience.

Highlights

• New Cleanup Script: A new TypeScript script, scripts/cleanup-branches.ts, has been added to automate the process of identifying and deleting old remote branches.
• Branch Deletion Criteria: The script identifies branches for deletion if they are older than 30 days, are not protected (e.g., main, master, release branches), and do not have an active open pull request associated with them.
• Interactive Confirmation and Batch Deletion: The script prompts the user for confirmation before proceeding with deletions and performs deletions in batches to avoid command line length limits. It also prunes local tracking branches after remote deletion.
• CLI Tool Dependencies: The script relies on the git and gh (GitHub CLI) tools being installed and accessible in the environment.

Changelog

• scripts/cleanup-branches.ts
  • Added a new script to identify and delete old remote branches based on age, protection status, and open PRs.
  • Implemented interactive confirmation for branch deletion.
  • Included batch processing for deleting multiple branches and local tracking branch pruning.

Activity

• No activity has been recorded on this pull request yet.

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-cli]

Hi @jacob314, thank you so much for your contribution to Gemini CLI! We really appreciate the time and effort you've put into this.

We're making some updates to our contribution process to improve how we track and review changes. Please take a moment to review our recent discussion post: Improving Our Contribution Process & Introducing New Guidelines.

Key Update: Starting January 26, 2026, the Gemini CLI project will require all pull requests to be associated with an existing issue. Any pull requests not linked to an issue by that date will be automatically closed.

Thank you for your understanding and for being a part of our community!

[gemini-code-assist]

Code Review

This pull request introduces a script to clean up old git branches. A high-severity command injection vulnerability was identified where branch names from the remote repository are concatenated into a shell command, potentially allowing arbitrary command execution. Additionally, an incorrect URL was found in the license header.

[github-actions]

Size Change: -2 B (0%)

Total Size: 25.9 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	25.4 MB	-2 B (0%)
./bundle/node_modules/@google/gemini-cli-devtools/dist/client/main.js	221 kB	0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/_client-assets.js	227 kB	0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/index.js	11.5 kB	0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/types.js	132 B	0 B
./bundle/sandbox-macos-permissive-open.sb	890 B	0 B
./bundle/sandbox-macos-permissive-proxied.sb	1.31 kB	0 B
./bundle/sandbox-macos-restrictive-open.sb	3.36 kB	0 B
./bundle/sandbox-macos-restrictive-proxied.sb	3.56 kB	0 B
./bundle/sandbox-macos-strict-open.sb	4.82 kB	0 B
./bundle/sandbox-macos-strict-proxied.sb	5.02 kB	0 B

_{compressed-size-action}

[scidomino]

do we actually need to keep "release" branches? Once we have the release tagged, I don't think the branch matters.