*: rename master branch to main (external repos)

.cci.jenkinsfile

@@ -1,4 +1,4 @@
-// Documentation: https://github.com/coreos/coreos-ci/blob/master/README-upstream-ci.md
+// Documentation: https://github.com/coreos/coreos-ci/blob/main/README-upstream-ci.md
 
 stage("Build") {
 parallel rpms: {

docs/CONTRIBUTING.md

@@ -25,4 +25,4 @@ See the [OSTree CONTRIBUTING][contributing] coding style.
 
 [rpm-ostree]: https://github.com/coreos/rpm-ostree
 [jenkinsfile]: https://github.com/coreos/rpm-ostree/blob/main/.cci.jenkinsfile
-[contributing]: https://github.com/ostreedev/ostree/blob/master/docs/CONTRIBUTING.md
+[contributing]: https://github.com/ostreedev/ostree/blob/main/docs/CONTRIBUTING.md

docs/administrator-handbook.md

@@ -59,7 +59,7 @@ getting exactly what you asked for.
 It is possible to dynamically add more packages onto the system that are not
 part of the commit composed on the server. These additional "layered" packages
 are persistent across upgrades, rebases, and deploys (contrast with the
-ostree [unlocking](https://github.com/ostreedev/ostree/blob/master/man/ostree-admin-unlock.xml) mechanism).
+ostree [unlocking](https://github.com/ostreedev/ostree/blob/main/man/ostree-admin-unlock.xml) mechanism).
 
 This is where the true hybrid image/package nature of rpm-ostree comes into
 play; you get a combination of the benefits of images and packages.  The

tests/common/libtest.cxx

@@ -23,7 +23,7 @@
 #include "libtest.h"
 
 /* Copied and adapted from:
- * https://github.com/ostreedev/ostree/blob/master/tests/libostreetest.c
+ * https://github.com/ostreedev/ostree/blob/main/tests/libostreetest.c
  *
  * This function hovers in a quantum superposition of horrifying and
  * beautiful.  Future generations may interpret it as modern art.

tests/common/libtest.h

@@ -21,7 +21,7 @@
  */
 
 /* Copied and adapted from:
- * https://github.com/ostreedev/ostree/blob/master/tests/libostreetest.c
+ * https://github.com/ostreedev/ostree/blob/main/tests/libostreetest.c
  */
 
 #pragma once