chore: move from master to main (#13127)

Author: Lyokone

.github/ISSUE_TEMPLATE/ios_background_message_handling.yml

@@ -124,7 +124,7 @@ body:
     attributes:
       label: Are you sending messages to your app from the Firebase Admin SDK?
       description: |
-        For an example of sending messages to your app, please see [FlutterFire's nodejs Firebase Admin SDK script](https://github.com/firebase/flutterfire/blob/master/packages/firebase_messaging/firebase_messaging/example/scripts/send-message.js). FlutterFire does not support sending messages from 3rd party packages.
+        For an example of sending messages to your app, please see [FlutterFire's nodejs Firebase Admin SDK script](https://github.com/firebase/flutterfire/blob/main/packages/firebase_messaging/firebase_messaging/example/scripts/send-message.js). FlutterFire does not support sending messages from 3rd party packages.
 
         It is essential you include the `contentAvailable` flag in your message payload when sending messages to your app from the Firebase Admin SDK.
 
@@ -201,8 +201,8 @@ body:
           5. Now send the message to your device
           6. Select all the rows on the logs & copy them, Cmd + C (not available on right-click menu)
 
-          [Example of successfully delivered data-only background message](https://github.com/firebase/flutterfire/blob/master/.github/images/ios-background-message-delivered.png)
-          [Example of unsuccessfully delivered data-only background message](https://github.com/firebase/flutterfire/blob/master/.github/images/ios-background-message-not-delivered.png)
+          [Example of successfully delivered data-only background message](https://github.com/firebase/flutterfire/blob/main/.github/images/ios-background-message-delivered.png)
+          [Example of unsuccessfully delivered data-only background message](https://github.com/firebase/flutterfire/blob/main/.github/images/ios-background-message-not-delivered.png)
 
           REQUIRED: Please paste your logs from the above steps in the text area so we can see if a message was delivered but not received by the background message handler.
     validations:

.github/PULL_REQUEST_TEMPLATE.md

@@ -29,7 +29,7 @@ Does your PR require plugin users to manually update their apps to accommodate y
 
 <!-- Links -->
 [issue database]: https://github.com/flutter/flutter/issues
-[Contributor Guide]: https://github.com/firebase/flutterfire/blob/master/CONTRIBUTING.md
+[Contributor Guide]: https://github.com/firebase/flutterfire/blob/main/CONTRIBUTING.md
 [Flutter Style Guide]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo
 [pub versioning philosophy]: https://dart.dev/tools/pub/versioning
 [CLA]: https://cla.developers.google.com/

.github/workflows/all_plugins.yaml

@@ -12,7 +12,7 @@ on:
       - '**.md'
   push:
     branches:
-      - master
+      - main
     paths-ignore:
       - 'docs/**'
       - 'website/**'

.github/workflows/e2e_tests.yaml

@@ -14,7 +14,7 @@ on:
       - '**.md'
   push:
     branches:
-      - master
+      - main
     paths-ignore:
       - 'docs/**'
       - 'website/**'

.github/workflows/ossf-scorecard.yml

@@ -12,7 +12,7 @@ on:
   schedule:
     - cron: '24 5 * * 5'
   push:
-    branches: [ "master" ]
+    branches: [ "main" ]
 
 # Declare default permissions as read only.
 permissions: read-all

CHANGELOG.md

@@ -3,7 +3,7 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
-## 2024-07-30 - [BoM 2.4.0](https://github.com/firebase/flutterfire/blob/master/VERSIONS.md#flutter-bom-240-2024-07-30)
+## 2024-07-30 - [BoM 2.4.0](https://github.com/firebase/flutterfire/blob/main/VERSIONS.md#flutter-bom-240-2024-07-30)
 
 ### Changes
 
@@ -148,7 +148,7 @@ Packages with dependency updates only:
  - **DOCS**(messaging,android): update inline documentation on behavior ([#12948](https://github.com/firebase/flutterfire/issues/12948)). ([8d7e2217](https://github.com/firebase/flutterfire/commit/8d7e2217446618b93c064933ef0bf2506c219275))
 
 
-## 2024-07-09 - [BoM 2.3.0](https://github.com/firebase/flutterfire/blob/master/VERSIONS.md#flutter-bom-230-2024-07-09)
+## 2024-07-09 - [BoM 2.3.0](https://github.com/firebase/flutterfire/blob/main/VERSIONS.md#flutter-bom-230-2024-07-09)
 
 ### Changes
 
@@ -302,7 +302,7 @@ Packages with dependency updates only:
  - **FIX**(storage,web): ensure exact same streams are not unsubscribed ([#13034](https://github.com/firebase/flutterfire/issues/13034)). ([20d00023](https://github.com/firebase/flutterfire/commit/20d000234072ece9def6c91bf4dfec57091ea8db))
 
 
-## 2024-06-25 - [BoM 2.2.0](https://github.com/firebase/flutterfire/blob/master/VERSIONS.md#flutter-bom-220-2024-06-25)
+## 2024-06-25 - [BoM 2.2.0](https://github.com/firebase/flutterfire/blob/main/VERSIONS.md#flutter-bom-220-2024-06-25)
 
 ### Changes
 
@@ -431,7 +431,7 @@ Packages with dependency updates only:
  - **FEAT**(storage,windows): add support for creationTime and updateTime ([#12966](https://github.com/firebase/flutterfire/issues/12966)). ([70a3fbc9](https://github.com/firebase/flutterfire/commit/70a3fbc97ec34c811616e92333aae299dd2ef569))
 
 
-## 2024-06-11 - [BoM 2.1.0](https://github.com/firebase/flutterfire/blob/master/VERSIONS.md#flutter-bom-210-2024-06-11)
+## 2024-06-11 - [BoM 2.1.0](https://github.com/firebase/flutterfire/blob/main/VERSIONS.md#flutter-bom-210-2024-06-11)
 
 ### Changes
 
@@ -609,7 +609,7 @@ Packages with other changes:
  - **FIX**(vertexai): fix the countTokens brokage ([#12899](https://github.com/firebase/flutterfire/issues/12899)). ([e946eb9b](https://github.com/firebase/flutterfire/commit/e946eb9b429da16bea617b68dda32f23d0deb5bc))
 
 
-## 2024-06-04 - [BoM 2.0.0](https://github.com/firebase/flutterfire/blob/master/VERSIONS.md#flutter-bom-200-2024-06-04)
+## 2024-06-04 - [BoM 2.0.0](https://github.com/firebase/flutterfire/blob/main/VERSIONS.md#flutter-bom-200-2024-06-04)
 
 ### Changes
 
@@ -827,7 +827,7 @@ Packages with dependency updates only:
  - **FIX**(web): fix some casting issue on Web JS Interop ([#12852](https://github.com/firebase/flutterfire/issues/12852)). ([4b56df1c](https://github.com/firebase/flutterfire/commit/4b56df1cc187d77ef22a82688a37f1c7aba4ed40))
 
 
-## 2024-05-28 - [BoM 1.1.0](https://github.com/firebase/flutterfire/blob/master/VERSIONS.md#flutter-bom-110-2024-05-28)
+## 2024-05-28 - [BoM 1.1.0](https://github.com/firebase/flutterfire/blob/main/VERSIONS.md#flutter-bom-110-2024-05-28)
 
 ### Changes
 

CONTRIBUTING.md

@@ -28,7 +28,7 @@ _See also: [Flutter's code of conduct](https://flutter.io/design-principles/#cod
   to generate an SSH key.
 - `git clone [email protected]:<your_name_here>/flutterfire.git`
 - `git remote add upstream [email protected]:firebase/flutterfire.git` (So that you
-  fetch from the master repository, not your clone, when running `git fetch`
+  fetch from the main repository, not your clone, when running `git fetch`
   et al.)
 
 ## 3. Environment Setup
@@ -174,7 +174,7 @@ For the rest of the plugins:
 melos run test:e2e:web
 ```
 
-A full list of all commands can be found within the [`melos.yaml`](https://github.com/firebase/flutterfire/blob/master/melos.yaml)
+A full list of all commands can be found within the [`melos.yaml`](https://github.com/firebase/flutterfire/blob/main/melos.yaml)
 file.
 
 ## 7. Contributing code
@@ -190,7 +190,7 @@ keep the code consistent and avoid common pitfalls.
 To start working on a patch:
 
 1. `git fetch upstream`
-2. `git checkout upstream/master -b <name_of_your_branch>`
+2. `git checkout upstream/main -b <name_of_your_branch>`
 3. Hack away!
 
 Once you have made your changes, ensure that it passes the internal analyzer & formatting checks. The following
@@ -279,12 +279,12 @@ generated via the commit types and changelogs via the commit messages.
 
 Some things to keep in mind before publishing the release:
 
-- Has CI ran on the master commit and gone green? Even if CI shows as green on
+- Has CI ran on the main commit and gone green? Even if CI shows as green on
   the PR it's still possible for it to fail on merge, for multiple reasons.
   There may have been some bug in the merge that introduced new failures. CI
   runs on PRs as it's configured on their branch state, and not on tip of tree.
   CI on PRs also only runs tests for packages that it detects have been directly
-  changed, vs running on every single package on master.
+  changed, vs running on every single package on main.
 - [Publishing is
   forever.](https://dart.dev/tools/pub/publishing#publishing-is-forever)
   Hopefully any bugs or breaking in changes in this PR have already been caught
@@ -297,29 +297,29 @@ Some things to keep in mind before publishing the release:
 
 ### Run a release...
 
-1. Switch to `master` branch locally.
-2. Run `git pull origin master`.
+1. Switch to `main` branch locally.
+2. Run `git pull origin main`.
 3. Run `git pull --tags` to make sure all tags are fetched.
 4. Create new branch with the signature "release/[year]-[month]-[day]".
 5. Push your branch to git running `git push origin [RELEASE BRANCH NAME]`.
 6. Run `melos version` to automatically version packages and update Changelogs.
 7. Run `melos publish` to dry run and confirm all packages are publishable.
 8. Run `melos bom [optional-version]` to update the `VERSIONS.md` and `scripts/versions.json` files.
 9. Run `git push origin [RELEASE BRANCH NAME]` & open pull request for review on GitHub.
-10. After successful review and merge of the pull request, switch to `master` branch locally, & run `git pull origin master`.
+10. After successful review and merge of the pull request, switch to `main` branch locally, & run `git pull origin main`.
 11. Run `melos publish --no-dry-run` to now publish to Pub.dev.
 12. Run `git push --tags` to push tags to repository.
 13. Ping @kevinthecheung to get the changelog in Firebase releases.
 
 ### Run a BoM release only...
 
-1. Switch to `master` branch locally.
-2. Run `git pull origin master`.
+1. Switch to `main` branch locally.
+2. Run `git pull origin main`.
 3. Run `git pull --tags` to make sure all tags are fetched.
 4. Create new branch with the signature "release/[year]-[month]-[day]-BoM".
 5. Run `melos bom [optional-version]` to update the `VERSIONS.md` and `scripts/versions.json` files.
 6. Push your branch to git running `git push origin [RELEASE BRANCH NAME]`.
-7. After successful review and merge of the pull request, switch to `master` branch locally, & run `git pull origin master`.
+7. After successful review and merge of the pull request, switch to `main` branch locally, & run `git pull origin main`.
 8. Run `git push --tags` to push tags to repository.
 9. Ping @kevinthecheung to get the changelog in Firebase releases.
 
@@ -328,8 +328,8 @@ Some things to keep in mind before publishing the release:
 Sometimes you may need to 'graduate' a package from a 'dev' or 'beta' (versions tagged like this: `0.10.0-dev.4`) to a stable version. Melos can also be used
 to graduate multiple packages using the following steps:
 
-1. Switch to `master` branch locally.
-2. Run 'git pull origin master'.
+1. Switch to `main` branch locally.
+2. Run 'git pull origin main'.
 3. Run `git fetch --all` to make sure all tags and commits are fetched.
 4. Run `melos version --graduate` to prompt a list of all packages to be graduated (You may also specifically select packages using the scope flag like this: `--scope="*firestore*"`)
 5. Run `git push --follow-tags` to push the auto commits and tags to the remote repository.