Follow master-to-main branch renaming

Author: ikesyo

.github/ISSUE_TEMPLATE

@@ -1,4 +1,4 @@
-- [ ] I have read [CONTRIBUTING](https://github.com/Quick/Nimble/blob/master/CONTRIBUTING.md) and have done my best to follow them.
+- [ ] I have read [CONTRIBUTING](https://github.com/Quick/Nimble/blob/main/CONTRIBUTING.md) and have done my best to follow them.
 
 ### What did you do?
 

.github/workflows/ci-swiftpm.yml

@@ -3,7 +3,7 @@ name: CI (SwiftPM)
 on:
   push:
     branches:
-      - master
+      - main
     tags:
       - "*"
   pull_request:

.github/workflows/ci-xcode.yml

@@ -3,7 +3,7 @@ name: CI (Xcode)
 on:
   push:
     branches:
-      - master
+      - main
     tags:
       - "*"
   pull_request:

.github/workflows/cocoapods.yml

@@ -3,7 +3,7 @@ name: CocoaPods
 on:
   push:
     branches:
-      - master
+      - main
     tags:
       - "*"
   pull_request:

CONTRIBUTING.md

@@ -68,7 +68,7 @@ Be sure to include in your issue:
   tests using `./test`.
 - If you've added a file to the project, make sure it's included in both
   the OS X and iOS targets.
-- The `master` branch will always support the stable Xcode version. Other
+- The `main` branch will always support the stable Xcode version. Other
   branches will point to their corresponding versions they support.
 - If you're making a configuration change, make sure to edit both the xcode
   project and the podspec file.
@@ -92,7 +92,7 @@ to the repository.
 Your conduct as a core member is your own responsibility, but here are
 some "ground rules":
 
-- Feel free to push whatever you want to master, and (if you have
+- Feel free to push whatever you want to main, and (if you have
   ownership permissions) to create any repositories you'd like.
 
   Ideally, however, all changes should be submitted as GitHub pull

README.md

@@ -1,6 +1,6 @@
 # Nimble
 
-[![Build Status](https://travis-ci.org/Quick/Nimble.svg?branch=master)](https://travis-ci.org/Quick/Nimble)
+[![Build Status](https://github.com/Quick/Nimble/actions/workflows/ci-xcode.yml/badge.svg)](https://github.com/Quick/Nimble/actions/workflows/ci-xcode.yml)
 [![CocoaPods](https://img.shields.io/cocoapods/v/Nimble.svg)](https://cocoapods.org/pods/Nimble)
 [![Carthage Compatible](https://img.shields.io/badge/Carthage-compatible-4BC51D.svg?style=flat)](https://github.com/Carthage/Carthage)
 [![Accio supported](https://img.shields.io/badge/Accio-supported-0A7CF5.svg?style=flat)](https://github.com/JamitLabs/Accio)
@@ -1335,7 +1335,7 @@ in an Xcode project you distribute to others.
   distribute it yourself via GitHub.
 
 For examples of how to write your own matchers, just check out the
-[`Matchers` directory](https://github.com/Quick/Nimble/tree/master/Sources/Nimble/Matchers)
+[`Matchers` directory](https://github.com/Quick/Nimble/tree/main/Sources/Nimble/Matchers)
 to see how Nimble's built-in set of matchers are implemented. You can
 also check out the tips below.
 
@@ -1636,7 +1636,7 @@ removed completely in Nimble v10.
 > Nimble can be used on its own, or in conjunction with its sister
   project, [Quick](https://github.com/Quick/Quick). To install both
   Quick and Nimble, follow [the installation instructions in the Quick
-  Documentation](https://github.com/Quick/Quick/blob/master/Documentation/en-us/InstallingQuick.md).
+  Documentation](https://github.com/Quick/Quick/blob/main/Documentation/en-us/InstallingQuick.md).
 
 Nimble can currently be installed in one of two ways: using CocoaPods, or with
 git submodules.

script/release

@@ -1,5 +1,5 @@
 #!/usr/bin/env sh
-REMOTE_BRANCH=master
+REMOTE_BRANCH=main
 POD_NAME=Nimble
 PODSPEC=Nimble.podspec