ENH move master to main

Author: beckermr

.ci_scripts/update_docs

@@ -30,21 +30,3 @@ rm -rf _build
 popd
 
 mv docs-README docs/README
-
-# git diff
-
-# # Only commit the docs for commits on master.
-# if [[ $GH_REF == refs/heads/master ]] && [[ $GH_TOKEN != "" ]]; then
-#     git add -A :/
-#     git commit -m "Re-ran make.py. [ci skip]" || true
-#     git remote add pushable https://${GH_TOKEN}@github.com/conda-forge/conda-forge.github.io.git/ > /dev/null
-#
-#     # Update the remotes before pushing and check the status.
-#     # This should give us more info if the push will not be
-#     # a simple fast-forward push.
-#     git fetch --all 2> /dev/null
-#     git branch -u pushable/gh-pages
-#     git status
-#     git push pushable new_site_content:gh-pages
-#     # 2> /dev/null
-# fi

.github/workflows/deploy.yml

@@ -3,7 +3,7 @@ name: deploy
 on:
   push:
     branches:
-      - master
+      - main
   pull_request: null
   workflow_dispatch: null
 
@@ -38,7 +38,7 @@ jobs:
           source ./.ci_scripts/update_docs
 
       - name: deploy
-        if: github.ref == 'refs/heads/master' && (github.event_name == 'push' || github.event_name == 'workflow_dispatch')
+        if: github.ref == 'refs/heads/main' && (github.event_name == 'push' || github.event_name == 'workflow_dispatch')
         uses: peaceiris/actions-gh-pages@v3
         with:
           github_token: ${{ secrets.GITHUB_TOKEN }}

README.md

@@ -35,4 +35,4 @@ A link to the google calendar item can be found [here](https://calendar.google.c
 
 We use https://hackmd.io/ for taking meeting minutes and will upload the resultant markdown file after the meeting has concluded.
 
-There is a template provided in [`misc/DEV_MEETING_TEMPLATE.md`](https://github.com/conda-forge/conda-forge.github.io/tree/master/misc/DEV_MEETING_TEMPLATE.md) that you should use to create a new hackmd document.
+There is a template provided in [`misc/DEV_MEETING_TEMPLATE.md`](https://github.com/conda-forge/conda-forge.github.io/tree/main/misc/DEV_MEETING_TEMPLATE.md) that you should use to create a new hackmd document.

newsfeed/demo/announcements.rst

@@ -105,7 +105,7 @@ Announcements
 
 :2020-07-15: ``CFEP-18:`` Removing static libraries from the main build
 
-    With `CFEP-18 <https://github.com/conda-forge/cfep/blob/master/cfep-18.md>`_
+    With `CFEP-18 <https://github.com/conda-forge/cfep/blob/main/cfep-18.md>`_
     we now have a policy on how to deal with static packages. The most important
     change here is that we will be removing static libraries from the main packages
     and moving them to ``-static`` suffixed packages. ``-static`` packages will not

src/index.rst

@@ -1,4 +1,4 @@
-.. conda-forge documentation master file, created by
+.. conda-forge documentation primary file, created by
    sphinx-quickstart on Wed Jun  1 01:44:13 2016.
    You can adapt this file completely to your liking, but it should at least
    contain the root `toctree` directive.

src/maintainer/infrastructure.rst

@@ -52,7 +52,7 @@ Documentation
 
 The documentation lives in `conda-forge/conda-forge.github.io <https://github.com/conda-forge/conda-forge.github.io/>`__, and is automatically deployed to our `online version <https://conda-forge.org/docs/>`__.
 
-The documentation is built with ``Sphinx`` and the sources files are located in the `src <https://github.com/conda-forge/conda-forge.github.io/tree/master/src>`__ directory of the repository.
+The documentation is built with ``Sphinx`` and the sources files are located in the `src <https://github.com/conda-forge/conda-forge.github.io/tree/main/src>`__ directory of the repository.
 
 If you found any typo error, unclear explanations or new topics that can be covered, you can suggest changes to the documentation. For more details, please refer to :ref:`improve_docs`.
 

src/maintainer/updating_pkgs.rst

@@ -205,7 +205,7 @@ remove broken packages from the ``main`` channel:
 
 1. Locate the paths to broken files on `anaconda.org <https://anaconda.org>`__, by searching for the conda-forge package and switching to the files tab.
 2. Fork `conda-forge/admin-requests <https://github.com/conda-forge/admin-requests>`__ and add a new text file in the ``broken`` directory.
-3. Add the broken files to the new text file, one path per line. See `broken/example.txt <https://github.com/conda-forge/admin-requests/blob/master/broken/example.txt>`__ for an example file.
+3. Add the broken files to the new text file, one path per line. See `broken/example.txt <https://github.com/conda-forge/admin-requests/blob/main/broken/example.txt>`__ for an example file.
 4. Open a new PR. Once merged, a bot will label all listed files as broken, thus effectively removing them from the channel.
 
 
@@ -224,19 +224,19 @@ Updating the maintainer list
 ============================
 
 The list of maintainers of a feedstock is recorded in the recipe itself. A new maintainer can be added by opening
-an issue in the feedstock repository with the following title: 
+an issue in the feedstock repository with the following title:
 
 ``@conda-forge-admin, please add user @username``
 
 where ``username`` is the username of the new maintainer to be added.
-A PR will be automatically created and a maintainer or a member of the ``core`` can then merge this PR to add the user. 
+A PR will be automatically created and a maintainer or a member of the ``core`` can then merge this PR to add the user.
 
 .. note::
 
 
    This PR is designed to skip building the package. Please do **not** modify it or adjust the commit message.
 
-For example see `this <https://github.com/conda-forge/cudnn-feedstock/issues/20>`__ issue. 
+For example see `this <https://github.com/conda-forge/cudnn-feedstock/issues/20>`__ issue.
 
 
 Maintaining several versions

src/misc/00_intro.rst

@@ -11,25 +11,25 @@ Glossary
 
   PR
     **P**\ ull **R**\ equest. Pull Request is a workflow method to submit contributions to an open development project in which the developer asks for changes committed to an external repository to be considered for inclusion in a project's main repository. `Learn More <https://help.github.com/articles/about-pull-requests/>`_.
-  
+
   CDT
     **C**\ ore **D**\ ependency **T**\ ree. Core Dependency Tree packages take care of the dependencies which are so close to the system that they are not packaged with ``conda-forge``. A CDT package consists of repackaged CentOS binaries from the appropriate version, either 6 or 7 depending on user choice and platform. `Learn More <https://conda-forge.org/docs/maintainer/knowledge_base.html#core-dependency-tree-packages-cdts/>`_.
 
   ABI
-    **A**\ pplication **B**\ inary **I**\ nterface. ABI is a document that comprehensively defines the binary system interface between applications and the operating system on which they run. `Learn More <https://en.wikipedia.org/wiki/Application_binary_interface>`_. 
-    
+    **A**\ pplication **B**\ inary **I**\ nterface. ABI is a document that comprehensively defines the binary system interface between applications and the operating system on which they run. `Learn More <https://en.wikipedia.org/wiki/Application_binary_interface>`_.
+
   ICU
-    **I**\ nternational **C**\ omponents for **U**\ nicode. ICU is an open-source project of mature C/C++ and Java libraries for Unicode support, software internationalization, and software globalization. `Learn More <http://site.icu-project.org/>`_. 
-    
+    **I**\ nternational **C**\ omponents for **U**\ nicode. ICU is an open-source project of mature C/C++ and Java libraries for Unicode support, software internationalization, and software globalization. `Learn More <http://site.icu-project.org/>`_.
+
   CRAN
     **C**\ omprehensive **R** **A**\ rchive **N**\ etwork. CRAN is a network of FTP and web servers around the world that store identical, up-to-date, versions of code and documentation for R. `Learn More <https://cran.r-project.org/>`_.
 
-  CFEP  
-    **C**\ onda **F**\ orge **E**\ nhancement **P**\ roposal. A CFEP is a document which outlines a suggested change to how the conda-forge project operates, from a technical standpoint as well as to address social topics such as governance and expected conduct. `Learn More <https://github.com/conda-forge/cfep/blob/master/cfep-01.md/>`_. 
+  CFEP
+    **C**\ onda **F**\ orge **E**\ nhancement **P**\ roposal. A CFEP is a document which outlines a suggested change to how the conda-forge project operates, from a technical standpoint as well as to address social topics such as governance and expected conduct. `Learn More <https://github.com/conda-forge/cfep/blob/main/cfep-01.md/>`_.
 
 TODO list
 *********
 
 .. todolist::
 
-The original entry is located in ``.src`` file of `/home/runner/work/conda-forge.github.io/conda-forge.github.io/src/maintainer/knowledge_base.rst, line 952. <https://github.com/conda-forge/conda-forge.github.io/blob/master/src/maintainer/knowledge_base.rst#noarch-generic/>`_.
+The original entry is located in ``.src`` file of `/home/runner/work/conda-forge.github.io/conda-forge.github.io/src/maintainer/knowledge_base.rst, line 952. <https://github.com/conda-forge/conda-forge.github.io/blob/main/src/maintainer/knowledge_base.rst#noarch-generic/>`_.

src/orga/governance.rst

@@ -91,7 +91,7 @@ and `the Helios voting system <https://vote.heliosvoting.org/>`_, but are
 open to any secure, anonymous system.) The email capability of your chosen
 voting platform should be used for sending voting invitations and reminders,
 and you should use the email list from
-https://github.com/conda-forge/conda-forge.github.io/blob/master/src/core.csv as
+https://github.com/conda-forge/conda-forge.github.io/blob/main/src/core.csv as
 the authoritative list of emails to use.
 
 The default voting period is 1 week (7 days). This may be modified at
@@ -114,7 +114,7 @@ To call for a standard vote, here is a template PR comment:
 
 :Posting results: To maintain the historical record, the outcome of any standard vote which invokes the
          "time out" rules below should be recorded in the "vote-results" folder at
-         https://github.com/conda-forge/conda-forge.github.io/tree/master/src/vote-results
+         https://github.com/conda-forge/conda-forge.github.io/tree/main/src/vote-results
 
          Each vote should be its own file.  The filename should reflect the topic and the
          date that the vote opened.  The file should contain at least:
@@ -187,7 +187,7 @@ To call for a standard vote, here is a template PR comment:
 
      To declare a standard vote "timed out," the person making such a declaration
      must post a pull-request adding
-     a vote record to the https://github.com/conda-forge/conda-forge.github.io/tree/master/src/vote-results
+     a vote record to the https://github.com/conda-forge/conda-forge.github.io/tree/main/src/vote-results
      folder.  The declaration PR should be merged by the first core member
      who is available to verify that
      the requirements for the timeout have been met, based on their

src/orga/subteams.rst

@@ -229,8 +229,8 @@ The staging team is responsible for:
 
 Members
 -------
-In addition to `core <https://github.com/conda-forge/conda-forge.github.io/blob/master/src/core.csv>`_
-and `emeritus <https://github.com/conda-forge/conda-forge.github.io/blob/master/src/emeritus.csv>`_,
+In addition to `core <https://github.com/conda-forge/conda-forge.github.io/blob/main/src/core.csv>`_
+and `emeritus <https://github.com/conda-forge/conda-forge.github.io/blob/main/src/emeritus.csv>`_,
 the following are members of the staged-recipes team and have commit rights.
 
  - Amir Mohammadi <[email protected]>
@@ -270,7 +270,7 @@ Diversity and Inclusion Sub-Team
 
 Role
 ----
-Develop ``conda-forge`` as a diverse community and advocate for 
+Develop ``conda-forge`` as a diverse community and advocate for
 actions impacting underrepresented groups in ``conda-forge``.
 
 Charter
@@ -282,7 +282,7 @@ Responsibility
 One of the core strengths of ``conda-forge`` is the diversity of ecosystems it supports.
 Likewise, fostering and advancing a diverse community of users, maintainers, and infrastructure contributors
 is an important part of creating and maintaining a vibrant project.
-The mandate of this subteam is to support and increase the diversity of the ``conda-forge`` 
+The mandate of this subteam is to support and increase the diversity of the ``conda-forge``
 community at all levels.
 As such this group can, but is not limited to:
 - provide a place for issues impacting diversity to be heard