chore: Update default branch to main

[lahirumaramba]

Updated default branch to main

If you have a local clone, you can update it by running the following commands:
master is now named main

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

Side note: Update the CI workflow to set the Java version to match the supported versions in firebase-tools

[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 systematically updates all mentions and configurations related to the default branch from master to main. This change ensures consistency across the repository's scripts and documentation, reflecting the modern standard for primary branch naming and streamlining future development workflows.

Highlights

• Default Branch Update: Updated references to the default branch from master to main in the publish_preflight_check.sh script, ensuring that CI/CD processes correctly fetch from the new primary branch.
• Documentation Alignment: Modified the CONTRIBUTING.md file to remove the explicit master branch reference from the pull request creation link, aligning the documentation with the new default branch name.

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 references from master to main to reflect the change in the default branch. The modifications in .github/scripts/publish_preflight_check.sh and CONTRIBUTING.md are correct and effectively implement this change. The update to the pull request link in CONTRIBUTING.md to be branch-agnostic is a good improvement. The changes look good to me.

[jonathanedey]

LGTM, Thanks! Could we add a note to the PR description to highlight why we needed to set the java version here for future reference.