master -> main (#333)

Author: zingale

.travis.yml

@@ -41,4 +41,4 @@ script:
 #   github-token: $GITHUB_TOKEN
 #   keep-history: true
 #   on:
-#     branch: master
+#     branch: main

README.md

@@ -1,4 +1,4 @@
-[![Build Status](https://travis-ci.org/starkiller-astro/Microphysics.svg?branch=master)](https://travis-ci.org/starkiller-astro/Microphysics) [![DOI](https://zenodo.org/badge/33425497.svg)](https://zenodo.org/badge/latestdoi/33425497)
+[![Build Status](https://travis-ci.org/starkiller-astro/Microphysics.svg?branch=main)](https://travis-ci.org/starkiller-astro/Microphysics) [![DOI](https://zenodo.org/badge/33425497.svg)](https://zenodo.org/badge/latestdoi/33425497)
 
 # Microphysics
 
@@ -90,13 +90,13 @@ Development generally follows the following ideas:
     change (or if they do, that the changes were expected).
 
     If a change is critical, we can cherry-pick the commit from
-    `development` to `master`.
+    `development` to `main`.
 
   * Contributions are welcomed from anyone. *Any contributions that
     have the potential to change answers should be done via pull
     requests.*   A pull request should be generated from your fork of
     `Microphysics` and target the `development` branch. (If you mistakenly
-    target `master`, we can change it for you.)
+    target `main`, we can change it for you.)
 
     Please add a line to `CHANGES` summarizing your change if it
     is a bug fix or new feature. Reference the PR or issue as
@@ -114,14 +114,14 @@ Development generally follows the following ideas:
     since these will be used for a squashed commit message.*
 
   * On the first workday of each month, we perform a merge of
-    `development` into `master`, in coordination with `AMReX`,
+    `development` into `main`, in coordination with `AMReX`,
     `Maestro`, and `Microphysics`. For this merge to take place, we
     need to be passing the regression tests.
 
     To accommodate this need, we close the merge window into
     `development` a few days before the merge day. While the merge
     window is closed, only bug fixes should be pushed into
-    `development`. Once the merge from `development` -> `master` is
+    `development`. Once the merge from `development` -> `main` is
     done, the merge window reopens.
 
 

sphinx_docs/source/conf.py

@@ -74,8 +74,8 @@ def get_version():
 # see https://github.com/phn/pytpm/issues/3#issuecomment-12133978
 numpydoc_show_class_members = False
 
-# The master toctree document.
-master_doc = 'index'
+# The main toctree document.
+main_doc = 'index'
 
 # General information about the project.
 project = 'StarKiller Microphysics'
@@ -192,7 +192,7 @@ def get_version():
 # (source start file, target name, title,
 #  author, documentclass [howto, manual, or own class]).
 latex_documents = [
-    (master_doc, 'StarKillerMicrophysics.tex', 'StarKiller Microphysics Documentation',
+    (main_doc, 'StarKillerMicrophysics.tex', 'StarKiller Microphysics Documentation',
      'StarKiller Development Team', 'manual'),
 ]
 
@@ -202,7 +202,7 @@ def get_version():
 # One entry per manual page. List of tuples
 # (source start file, name, description, authors, manual section).
 man_pages = [
-    (master_doc, 'starkillermicrophysics', 'StarKiller Microphysics Documentation',
+    (main_doc, 'starkillermicrophysics', 'StarKiller Microphysics Documentation',
      [author], 1)
 ]
 
@@ -213,7 +213,7 @@ def get_version():
 # (source start file, target name, title, author,
 #  dir menu entry, description, category)
 texinfo_documents = [
-    (master_doc, 'StarKillerMicrophysics', 'StarKiller Microphysics Documentation',
+    (main_doc, 'StarKillerMicrophysics', 'StarKiller Microphysics Documentation',
      author, 'StarKillerMicrophysics', 'One line description of project.',
      'Miscellaneous'),
 ]

sphinx_docs/source/index.rst

@@ -1,4 +1,4 @@
-.. StarKiller documentation master file.
+.. StarKiller documentation main file.
    You can adapt this file completely to your liking, but it should at least
    contain the root `toctree` directive.