Rename master branch to main

Signed-off-by: Lee Smet <lee.smet@hotmail.com>

Author: LeeSmet

.github/workflows/ci.yaml

@@ -2,9 +2,9 @@ name: ci
 
 on:
   push:
-    branches: [ master ]
+    branches: [ main ]
   pull_request:
-    branches: [ master ]
+    branches: [ main ]
 
 env:
   CARGO_TERM_COLOR: always

.github/workflows/docker.yml

@@ -4,7 +4,7 @@ name: Create and publish a Docker image
 # Configures this workflow to run every time a change is pushed to the branch called `release`.
 on:
   push:
-    branches: ['master']
+    branches: ['main']
 
 # Defines two custom environment variables for the workflow. These are used for the Container registry domain, and a name for the Docker image that this workflow builds.
 env:

README.md

@@ -27,7 +27,7 @@ make run
 
 > We are looking for lots of testers to push the system
 
-> [see here for docs](https://github.com/threefoldtech/mycelium/tree/master/docs)
+> [see here for docs](https://github.com/threefoldtech/mycelium/tree/main/docs)
 
 ## Running
 

docs/api.yaml

@@ -7,7 +7,7 @@ info:
     url: "https://github.com/threefoldtech/mycelium"
   license:
     name: Apache 2.0
-    url: "https://github.com/threefoldtech/mycelium/blob/master/LICENSE"
+    url: "https://github.com/threefoldtech/mycelium/blob/main/LICENSE"
 
   description: |
     This is the specification of the **mycelium** management API. It is used to perform admin tasks on the system, and

docs/openrpc.json

@@ -9,7 +9,7 @@
     },
     "license": {
       "name": "Apache 2.0",
-      "url": "https://github.com/threefoldtech/mycelium/blob/master/LICENSE"
+      "url": "https://github.com/threefoldtech/mycelium/blob/main/LICENSE"
     }
   },
   "servers": [

myceliumd-private/README.md

@@ -2,9 +2,9 @@
 
 This is the main binary to use when connecting to [a private network](../docs/private_network.md).
 You can either get a release from [the GitHub release page](https://github.com/threefoldtech/myceliumd/releases), 
-or build the code yourself here. While we intend to keep the master branch as stable,
-i.e. a build from latest master should succeed, this is not a hard guarantee. Additionally,
-the master branch might not be compatible with the latest release, in case of a
+or build the code yourself here. While we intend to keep the main branch as stable,
+i.e. a build from latest main should succeed, this is not a hard guarantee. Additionally,
+the main branch might not be compatible with the latest release, in case of a
 breaking change.
 
 Building, with the rust toolchain installed, can be done by running `cargo build`

myceliumd/README.md

@@ -2,9 +2,9 @@
 
 This is the main binary to use for joining a/the public [`mycelium`] network. You can
 either get the latest release from [the GitHub release page](https://github.com/threefoldtech/myceliumd/releases/latest),
-or build the code yourself here. While we intend to keep the master branch as stable,
-i.e. a build from latest master should succeed, this is not a hard guarantee. Additionally,
-the master branch might not be compatible with the latest release, in case of a
+or build the code yourself here. While we intend to keep the main branch as stable,
+i.e. a build from latest main should succeed, this is not a hard guarantee. Additionally,
+the main branch might not be compatible with the latest release, in case of a
 breaking change.
 
 Building, with the rust toolchain installed, can be done by running `cargo build`