fix: rename default branch to main

Author: mikehardy

.github/workflows/linting.yml

@@ -6,7 +6,7 @@ on:
       - '**'
   push:
     branches:
-      - master
+      - main
 
 jobs:
   linting:

.github/workflows/publish.yml

@@ -4,7 +4,7 @@ on:
   workflow_dispatch:
   push:
     branches:
-      - master
+      - main
 
 jobs:
   publish_npm:
@@ -15,7 +15,7 @@ jobs:
     steps:
       - uses: actions/checkout@v2
         with:
-          ref: 'master'
+          ref: 'main'
           fetch-depth: 0
       - name: Yarn Install
         uses: nick-invision/retry@v2

.github/workflows/tests_e2e_android.yml

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

.github/workflows/tests_e2e_ios.yml

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

.github/workflows/tests_jest.yml

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

CONTRIBUTING.md

@@ -6,7 +6,7 @@ We welcome any type of contribution, not just code. You can help with;
 
 - **QA**: file bug reports, the more details you can give the better (e.g. platform versions, screenshots SDK versions & logs)
 - **Docs**: improve reference coverage, add more examples, fix typos or anything else you can spot.
-  - At the top of every page on our docs site you can click the `Edit Page` button to go to that pages markdown file or TypeScript definition file, or view the [documents](https://github.com/invertase/react-native-firebase/tree/master/docs) directly
+  - At the top of every page on our docs site you can click the `Edit Page` button to go to that pages markdown file or TypeScript definition file, or view the [documents](https://github.com/invertase/react-native-firebase/tree/main/docs) directly
 - **Community**: presenting the project at meetups, organizing a dedicated meetup for the local community, ...
 - **Code**: take a look at the [open issues](issues). Even if you can't write code, commenting on them, showing that you care about a given issue matters.
 
@@ -133,14 +133,14 @@ To run end-to-end tests for `iOS`, please run:
 - `yarn tests:emulator:start` - runs Firestore emulator for Firestore tests.
 - `yarn tests:ios:test` - runs tests using Detox library. Tests for each package can be found in the `e2e` directory (i.e. `[PACKAGE]/e2e/*.e2e.js`)
 
-See it's local testing guide [here](https://github.com/invertase/react-native-firebase/blob/master/tests/README.md) to get started
+See it's local testing guide [here](https://github.com/invertase/react-native-firebase/blob/main/tests/README.md) to get started
 with `e2e` testing this project.
 
 ---
 
 ## Submitting code for review
 
-All code changes should be submitted as a pull request to the master branch.
+All code changes should be submitted as a pull request to the main branch.
 
 The bigger the pull request, the longer it will take to review and merge. Try to break down large pull requests in smaller chunks that are easier to review and merge. It is also always helpful to have some context for your pull request. What was the purpose? Why does it matter to you? Tag in any linked issues.
 
@@ -164,7 +164,7 @@ See the [Conventional Commits](https://www.conventionalcommits.org/) specificati
 
 ### Code review process
 
-Pull Requests to master require two or more peer-review approvals and passing status checks before they can be merged.
+Pull Requests to main require two or more peer-review approvals and passing status checks before they can be merged.
 
 Reviews of Pull Requests are based on the following acceptance critical:
 
@@ -181,7 +181,7 @@ Reviews of Pull Requests are based on the following acceptance critical:
   - Other tests through Jest.
 - Do all CI checks pass.
 
-Once a PR is merged into master; new versions of the changed packages are automatically created and published to NPM.
+Once a PR is merged into main; new versions of the changed packages are automatically created and published to NPM.
 
 ## [No Brown M&M's](http://en.wikipedia.org/wiki/Van_Halen#Contract_riders)
 

README.md

@@ -69,12 +69,12 @@ Looking for the Version 5 documentation? [View legacy documentation](https://v5.
 
 ## Contributing
 
-- [Overview](https://github.com/invertase/react-native-firebase/blob/master/CONTRIBUTING.md)
+- [Overview](https://github.com/invertase/react-native-firebase/blob/main/CONTRIBUTING.md)
 - [Issues](https://github.com/invertase/react-native-firebase/issues)
 - [PRs](https://github.com/invertase/react-native-firebase/pulls)
 - [Documentation](https://rnfirebase.io)
-- [Community](https://github.com/invertase/react-native-firebase/blob/master/CONTRIBUTING.md)
-- [Code of Conduct](https://github.com/invertase/meta/blob/master/CODE_OF_CONDUCT.md)
+- [Community](https://github.com/invertase/react-native-firebase/blob/main/CONTRIBUTING.md)
+- [Code of Conduct](https://github.com/invertase/meta/blob/main/CODE_OF_CONDUCT.md)
 
 ## License
 

docs/auth/social-auth.md

@@ -22,7 +22,7 @@ Once authentication is successful, a Firebase credential can be used to sign the
 
 To get started, you must first install the [`react-native-apple-authentication`](https://github.com/invertase/react-native-apple-authentication)
 library. There are a number of [prerequisites](https://github.com/invertase/react-native-apple-authentication#prerequisites-to-using-this-library) to using the library, including
-[setting up your Apple Developer account](https://github.com/invertase/react-native-apple-authentication/blob/master/docs/INITIAL_SETUP.md) to enable Apple Sign-In.
+[setting up your Apple Developer account](https://github.com/invertase/react-native-apple-authentication/blob/main/docs/INITIAL_SETUP.md) to enable Apple Sign-In.
 
 Ensure the "Apple" sign-in provider is enabled on the [Firebase Console](https://console.firebase.google.com/project/_/authentication/providers).
 

docs/messaging/usage/index.md

@@ -438,7 +438,7 @@ On Android, any messages which display a [Notification](/messaging/notifications
 (such as the small icon, title etc). To provide a custom tint color, update the `messaging_android_notification_color` property
 with a Android color resource name.
 
-The library provides a set of [predefined colors](https://github.com/invertase/react-native-firebase/blob/master/packages/messaging/android/src/main/res/values/colors.xml) corresponding to the [HTML colors](https://www.w3schools.com/colors/colors_names.asp) for convenience, for example:
+The library provides a set of [predefined colors](https://github.com/invertase/react-native-firebase/blob/main/packages/messaging/android/src/main/res/values/colors.xml) corresponding to the [HTML colors](https://www.w3schools.com/colors/colors_names.asp) for convenience, for example:
 
 ```json
 // <projectRoot>/firebase.json

docs/ml/usage/index.md

@@ -25,7 +25,7 @@ cd ios/ && pod install
 > **This package is mostly discontinued** since these APIs are no longer available in the latest Firebase SDKs.
 > To call the Cloud Vision API from your app the recommended approach is using Firebase
 > Authentication and Functions, which gives you a managed, serverless gateway to Google Cloud Vision APIs. For an example
-> Functions project see the [vision-annotate-images](https://github.com/firebase/functions-samples/tree/master/vision-annotate-images) sample project.
+> Functions project see the [vision-annotate-images](https://github.com/firebase/functions-samples/tree/main/vision-annotate-images) sample project.
 
 If you're using an older version of React Native without autolinking support, or wish to integrate into an existing project,
 you can follow the manual installation steps for [iOS](/ml/usage/installation/ios) and [Android](/ml/usage/installation/android).