Skip to content

Conversation

@lahirumaramba
Copy link
Member

@lahirumaramba lahirumaramba commented Dec 12, 2025

Updated default branch name to main

If you have a local clone, you can update it by running the following commands:

git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a

Optionally, run the following command to remove tracking references to the old branch name.

git remote prune origin

@gemini-code-assist
Copy link

Summary of Changes

Hello @lahirumaramba, 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 systematically updates all references to the default branch from 'master' to 'main' across the repository. This change impacts CI/CD scripts, release preparation tools, and contributor documentation, ensuring consistency with the new branch name and promoting inclusive language practices within the project.

Highlights

  • Default Branch Renaming: The project's default branch has been renamed from 'master' to 'main' to align with modern naming conventions.
  • Script Updates: Internal scripts, including 'publish_preflight_check.sh' and 'prepare_release.sh', have been updated to reference the new 'main' branch.
  • Documentation Alignment: The 'CONTRIBUTING.md' file has been modified to reflect the default branch change, specifically in the pull request creation link.
Ignored Files
  • Ignored by pattern: .github/workflows/** (2)
    • .github/workflows/nightly.yml
    • .github/workflows/release.yml
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 updates the repository to reflect the change of the default branch from master to main. The changes in the shell scripts and the CONTRIBUTING.md file correctly replace references to master with main or use a branch-agnostic URL. The changes are correct and align with the PR's objective. I've added one suggestion to improve the robustness of a script. Overall, this is a good and necessary maintenance update.

Comment on lines +109 to +112
# Ensure the checked out branch is main
CHECKED_OUT_BRANCH="$(git branch | grep "*" | awk -F ' ' '{print $2}')"
if [[ $CHECKED_OUT_BRANCH != "master" ]]; then
read -p "[WARN] You are on the '${CHECKED_OUT_BRANCH}' branch, not 'master'. Continue? (y/N) " CONTINUE
if [[ $CHECKED_OUT_BRANCH != "main" ]]; then
read -p "[WARN] You are on the '${CHECKED_OUT_BRANCH}' branch, not 'main'. Continue? (y/N) " CONTINUE

Choose a reason for hiding this comment

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

medium

The method for getting the current branch name is not very robust. It can fail in certain scenarios like a detached HEAD state. A more reliable way is to use git rev-parse --abbrev-ref HEAD.

Also, it's good practice to quote shell variables when they are used to prevent issues with spaces or other special characters in the value.

Suggested change
# Ensure the checked out branch is main
CHECKED_OUT_BRANCH="$(git branch | grep "*" | awk -F ' ' '{print $2}')"
if [[ $CHECKED_OUT_BRANCH != "master" ]]; then
read -p "[WARN] You are on the '${CHECKED_OUT_BRANCH}' branch, not 'master'. Continue? (y/N) " CONTINUE
if [[ $CHECKED_OUT_BRANCH != "main" ]]; then
read -p "[WARN] You are on the '${CHECKED_OUT_BRANCH}' branch, not 'main'. Continue? (y/N) " CONTINUE
# Ensure the checked out branch is main
CHECKED_OUT_BRANCH="$(git rev-parse --abbrev-ref HEAD)"
if [[ "$CHECKED_OUT_BRANCH" != "main" ]]; then
read -p "[WARN] You are on the '${CHECKED_OUT_BRANCH}' branch, not 'main'. Continue? (y/N) " CONTINUE

Copy link
Contributor

@jonathanedey jonathanedey left a comment

Choose a reason for hiding this comment

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

LGTM Thanks!

@lahirumaramba lahirumaramba merged commit 6cf4da3 into main Dec 15, 2025
5 checks passed
@lahirumaramba lahirumaramba deleted the lm-rename-main branch December 15, 2025 15:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release:stage Stage a release candidate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants