code changes for changing the name of the "master" branch to "main" (#1122)

* update github python package.yml
* update the README
* update contributing and architecture links

Author: ssteinbach

.github/workflows/python-package.yml

@@ -11,9 +11,9 @@ env:
 
 on:
   push:
-    branches: [ master ]
+    branches: [ main ]
   pull_request:
-    branches: [ master ]
+    branches: [ main ]
 
 jobs:
   cpp_build:

README.md

@@ -6,7 +6,7 @@ OpenTimelineIO
 [![Supported VFX Platform Versions](https://img.shields.io/badge/vfx%20platform-2018--2021-lightgrey.svg)](http://www.vfxplatform.com/)
 ![Supported Versions](https://img.shields.io/badge/python-2.7%2C%203.7%2C%203.8%2C%203.9-blue)
 [![Build Status](https://github.com/PixarAnimationStudios/OpenTimelineIO/actions/workflows/python-package.yml/badge.svg)](https://github.com/PixarAnimationStudios/OpenTimelineIO/actions/workflows/python-package.yml)
-[![codecov](https://codecov.io/gh/PixarAnimationStudios/OpenTimelineIO/branch/master/graph/badge.svg)](https://codecov.io/gh/PixarAnimationStudios/OpenTimelineIO)
+[![codecov](https://codecov.io/gh/PixarAnimationStudios/OpenTimelineIO/branch/main/graph/badge.svg)](https://codecov.io/gh/PixarAnimationStudios/OpenTimelineIO)
 [![docs](https://readthedocs.org/projects/opentimelineio/badge/?version=latest)](https://opentimelineio.readthedocs.io/en/latest/index.html)
 
 Main web site: http://opentimeline.io/
@@ -96,10 +96,10 @@ for clip in timeline.each_clip():
   print(clip.name, clip.duration())
 ```
 
-There are more code examples here: https://github.com/PixarAnimationStudios/OpenTimelineIO/tree/master/examples
+There are more code examples here: https://github.com/PixarAnimationStudios/OpenTimelineIO/tree/main/examples
 
 Also, looking through the unit tests is a great way to see what OTIO can do:
-https://github.com/PixarAnimationStudios/OpenTimelineIO/tree/master/tests
+https://github.com/PixarAnimationStudios/OpenTimelineIO/tree/main/tests
 
 OTIO includes a viewer program as well (see the quickstart section for instructions on installing it):
 

docs/conf.py

@@ -50,7 +50,7 @@
 # The encoding of source files.
 # source_encoding = 'utf-8-sig'
 
-# The master toctree document.
+# The main toctree document.
 master_doc = 'index'
 
 # General information about the project.

docs/tutorials/architecture.md

@@ -134,4 +134,4 @@ For more information about writing media linkers, see <a href="write-a-media-lin
 Example Scripts
 ----------------
 
-Example scripts are located in the <a href="https://github.com/PixarAnimationStudios/OpenTimelineIO/tree/master/examples" target="_blank">examples subdirectory</a>.
+Example scripts are located in the <a href="https://github.com/PixarAnimationStudios/OpenTimelineIO/tree/main/examples" target="_blank">examples subdirectory</a>.

docs/tutorials/contributing.md

@@ -7,8 +7,8 @@ We're excited to collaborate with the community and look forward to the many imp
 
 Before contributing code to OpenTimelineIO, we ask that you sign a Contributor License Agreement (CLA).  At the root of the repo you can find the two possible CLAs:
 
-* [OTIO_CLA_Corporate.pdf](https://github.com/PixarAnimationStudios/OpenTimelineIO/raw/master/OTIO_CLA_Corporate.pdf): please sign this one for corporate use
-* [OTIO_CLA_Individual.pdf](https://github.com/PixarAnimationStudios/OpenTimelineIO/raw/master/OTIO_CLA_Individual.pdf): please sign this one if you're an individual contributor
+* [OTIO_CLA_Corporate.pdf](https://github.com/PixarAnimationStudios/OpenTimelineIO/raw/main/OTIO_CLA_Corporate.pdf): please sign this one for corporate use
+* [OTIO_CLA_Individual.pdf](https://github.com/PixarAnimationStudios/OpenTimelineIO/raw/main/OTIO_CLA_Individual.pdf): please sign this one if you're an individual contributor
 
 Once your CLA is signed, send it to `[email protected]` (please make sure to include your github username) and wait for confirmation that we've received it.  After that, you can submit pull requests.
 
@@ -42,13 +42,13 @@ Now you fetch the latest changes from Pixar's OpenTimelineIO repo like this:
 
 ```bash
 git fetch upstream
-git merge upstream/master
+git merge upstream/main
 ```
 
-All the development should happen against the `master` branch.  We recommend you create a new branch for each feature or fix that you'd like to make and give it a descriptive name so that you can remember it later.  You can checkout a new branch and create it simultaneously like this:
+All the development should happen against the `main` branch.  We recommend you create a new branch for each feature or fix that you'd like to make and give it a descriptive name so that you can remember it later.  You can checkout a new branch and create it simultaneously like this:
 
 ```bash
-git checkout -b mybugfix upstream/master
+git checkout -b mybugfix upstream/main
 ```
 
 Now you can work in your branch locally.
@@ -66,6 +66,6 @@ If all the tests pass and you'd like to send your change in for consideration, p
 git push origin mybugfix
 ```
 
-Now your remote branch will have your `mybugfix` branch, which you can now pull request (to OpenTimelineIO's `master` branch) using the github UI.
+Now your remote branch will have your `mybugfix` branch, which you can now pull request (to OpenTimelineIO's `main` branch) using the github UI.
 
 Please make sure that your pull requests are clean.  Use the rebase and squash git facilities as needed to ensure that the pull request is as clean as possible.