chore: Rename default branch to main

[lahirumaramba]

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]

Summary of Changes

Hello @lahirumaramba, 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 updates the repository's configuration and documentation to reflect the change of the default branch name from master to main. The changes ensure that automated scripts and contributor guidelines correctly point to the new primary development branch, maintaining operational consistency and aligning with modern naming conventions.

Highlights

• Script Updates for Branch Name: Modified internal shell scripts (publish_preflight_check.sh and prepare_release.sh) to reference the new default branch name, main, instead of master for Git operations like fetching, checking out, and creating new branches.
• Documentation Alignment: Updated the CONTRIBUTING.md file to remove the explicit master branch reference from the pull request submission link, ensuring the documentation is consistent with the new default branch naming convention.

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. ↩

[gemini-code-assist]

Code Review

This pull request updates repository configurations and documentation to reflect the change of the default branch from master to main. The changes in the shell scripts and markdown files are correct. I have one suggestion for prepare_release.sh to make the release process more robust by creating the release branch directly from the remote tracking branch.

[lahirumaramba]

/gemini review

[gemini-code-assist]

Code Review

This pull request correctly renames the default branch from master to main across the repository's scripts and documentation. The changes are accurate and well-implemented. In prepare_release.sh, the git commands have been refactored to be more robust, which is a good improvement. The update to CONTRIBUTING.md makes the pull request link branch-agnostic, which is also a positive change. Overall, this is a solid maintenance update with no issues found.

[jonathanedey]

LGTM Thanks!