chore: rename master to main (#1364)

Author: madsroskar

.github/workflows/changelog-preview.yml

@@ -3,7 +3,7 @@ name: Changelog preview
 on:
   pull_request:
     branches:
-      - master
+      - main
     types: [opened, synchronize]
 
 jobs:

.github/workflows/check-pr.yml

@@ -4,7 +4,7 @@ on:
   pull_request:
     branches:
       - develop
-      - master
+      - main
       - 'v[0-9]+.[0-9]+.[0-9]+*beta*'
     types: [opened, synchronize]
 

.github/workflows/docusaurus.yml

@@ -3,7 +3,7 @@ name: docusaurus
 on:
   push:
     branches:
-      - master # default branch name for each repo that docs should be push from
+      - main # default branch name for each repo that docs should be push from
       - develop
     paths:
       - docusaurus/**
@@ -15,6 +15,6 @@ jobs:
       - name: push
         uses: GetStream/push-stream-chat-docusaurus-action@main
         with:
-          target-branch: ${{ github.ref == 'refs/heads/master' && 'production' || 'staging' }}
+          target-branch: ${{ github.ref == 'refs/heads/main' && 'production' || 'staging' }}
         env:
           DOCUSAURUS_GH_TOKEN: ${{ secrets.DOCUSAURUS_GH_TOKEN }}

.github/workflows/release.yml

@@ -3,7 +3,7 @@ name: Release
 on:
  push:
    branches:
-     - master
+     - main
 
 jobs:
  publish-release:
@@ -42,5 +42,5 @@ jobs:
          git stash
          git checkout develop
          git pull origin develop
-         git merge master -m "chore: merge back release [skip ci]"
+         git merge main -m "chore: merge back release [skip ci]"
          git push origin develop

README.md

@@ -1,15 +1,15 @@
 # Official React Native SDK for Stream Chat
 
 <p align="center">
-  <a href="https://getstream.io/chat/react-native-chat/tutorial/"><img src="https://github.com/GetStream/stream-chat-react-native/blob/master/screenshots/readme/cover.png" alt="react native chat" width="100%" /></a>
+  <a href="https://getstream.io/chat/react-native-chat/tutorial/"><img src="https://github.com/GetStream/stream-chat-react-native/blob/main/screenshots/readme/cover.png" alt="react native chat" width="100%" /></a>
 </p>
 
 > The official React Native and Expo components for Stream Chat, a service for
 > building chat applications.
 
 
 [![NPM](https://img.shields.io/npm/v/stream-chat-react-native.svg)](https://www.npmjs.com/package/stream-chat-react-native)
-[![Build Status](https://github.com/GetStream/stream-chat-react-native/workflows/test/badge.svg?branch=master)](https://github.com/GetStream/stream-chat-react-native/actions)
+[![Build Status](https://github.com/GetStream/stream-chat-react-native/workflows/test/badge.svg?branch=main)](https://github.com/GetStream/stream-chat-react-native/actions)
 [![Component Reference](https://img.shields.io/badge/docs-component%20reference-blue.svg)](https://getstream.io/chat/docs/sdk/reactnative)
 
 <img align="right" src="https://getstream.imgix.net/images/ios-chat-tutorial/[email protected]?auto=format,enhance" width="50%" />
@@ -68,7 +68,7 @@ We welcome code changes that improve this library or fix a problem, and please m
 
 ## Git flow & Release process
 
-We enforce conventional commits and have an automated releasing process using workspaces and semantic-release. Read our [git flow & release process guide](https://github.com/GetStream/stream-chat-react-native/blob/master/RELEASE_PROCESS.md) for more information
+We enforce conventional commits and have an automated releasing process using workspaces and semantic-release. Read our [git flow & release process guide](https://github.com/GetStream/stream-chat-react-native/blob/main/RELEASE_PROCESS.md) for more information
 
 ## We are hiring
 

RELEASE_PROCESS.md

@@ -21,9 +21,9 @@ Please have in mind that the only line you have to add is the selected one. Gith
 
 If you've released something you were not supposed to and want to remove that release from npm, remove the git tag and then rollback the changes, you have a few options:
 
-### Reset master branch
+### Reset main branch
 
-Cleanest way is to just reset the master branch and remove the last few commits, so the ideal is just do reset and force-push.
+Cleanest way is to just reset the main branch and remove the last few commits, so the ideal is just do reset and force-push.
 
 ### Revert unwanted commits
 
@@ -35,15 +35,15 @@ If you want some of the newest commits but want to remove older ones you can jus
 
 All pull requests should point to the `develop` branch. Everytime it is updated, a new `next` version is created and released to npm using the latest commit sha.
 
-### master & release candidates
+### main & release candidates
 
-Everytime we want to push things to master, we should create a pull request from develop to master. When that PR is opened/updated, a comment will be 
+Everytime we want to push things to main, we should create a pull request from develop to main. When that PR is opened/updated, a comment will be 
 added/updated containing the changelog that will be generated by merging that PR. This is useful for knowing whats going to be released if we decide to
-press the merge button. By doing that, a release candidate tag is created and flagged with the `rc` tag on npm. Also, a `merge back pull request` is created from master to develop.
+press the merge button. By doing that, a release candidate tag is created and flagged with the `rc` tag on npm. Also, a `merge back pull request` is created from main to develop.
 
 ## Graduating release candidates to production
 
 Once the release candidate is well tested and approved, the manual release workflow can be triggered through the Github actions UI. It should always be pointed
-to master and it will `graduate the latest release candidate` to an actual release, flagging it with the `latest` tag on npm. Also, a `merge back pull request` 
-is created from master to develop.
+to main and it will `graduate the latest release candidate` to an actual release, flagging it with the `latest` tag on npm. Also, a `merge back pull request` 
+is created from main to develop.
 

docs/build/bundle.38535de9.js

@@ -8,7 +8,7 @@ object-assign
  * @overview es6-promise - a tiny implementation of Promises/A+.
  * @copyright Copyright (c) 2014 Yehuda Katz, Tom Dale, Stefan Penner and contributors (Conversion to ES6 API by Jake Archibald)
  * @license   Licensed under MIT license
- *            See https://raw.githubusercontent.com/stefanpenner/es6-promise/master/LICENSE
+ *            See https://raw.githubusercontent.com/stefanpenner/es6-promise/main/LICENSE
  * @version   v4.2.8+1e68dce6
  */
 
@@ -42,7 +42,7 @@ object-assign
 /*!
  * regjsgen 0.5.2
  * Copyright 2014-2020 Benjamin Tan <https://ofcr.se/>
- * Available under the MIT license <https://github.com/bnjmnt4n/regjsgen/blob/master/LICENSE-MIT.txt>
+ * Available under the MIT license <https://github.com/bnjmnt4n/regjsgen/blob/main/LICENSE-MIT.txt>
  */
 
 /*! https://mths.be/regenerate v1.4.1 by @mathias | MIT license */

docs/build/bundle.38535de9.js.LICENSE.txt

@@ -8,7 +8,7 @@ object-assign
  * @overview es6-promise - a tiny implementation of Promises/A+.
  * @copyright Copyright (c) 2014 Yehuda Katz, Tom Dale, Stefan Penner and contributors (Conversion to ES6 API by Jake Archibald)
  * @license   Licensed under MIT license
- *            See https://raw.githubusercontent.com/stefanpenner/es6-promise/master/LICENSE
+ *            See https://raw.githubusercontent.com/stefanpenner/es6-promise/main/LICENSE
  * @version   v4.2.8+1e68dce6
  */
 
@@ -42,7 +42,7 @@ object-assign
 /*!
  * regjsgen 0.5.2
  * Copyright 2014-2020 Benjamin Tan <https://ofcr.se/>
- * Available under the MIT license <https://github.com/bnjmnt4n/regjsgen/blob/master/LICENSE-MIT.txt>
+ * Available under the MIT license <https://github.com/bnjmnt4n/regjsgen/blob/main/LICENSE-MIT.txt>
  */
 
 /*! clipboard-copy. MIT License. Feross Aboukhadijeh <https://feross.org/opensource> */