refactor(docs): update references to main branch

Author: thekaveman

docs/README.md

@@ -2,7 +2,7 @@
 
 This website provides technical documentation for the `eligibility-server` application, a part of the [`benefits`](https://docs.calitp.org/benefits) application, from the [California Integrated Travel Project (Cal-ITP)](https://www.calitp.org).
 
-Documentation for the `dev` (default) branch is available [online](https://docs.calitp.org/eligibility-server).
+Documentation for the `main` (default) branch is available [online](https://docs.calitp.org/eligibility-server).
 
 ## Overview
 

docs/configuration/README.md

@@ -14,7 +14,7 @@ If you want to run with different settings, you should:
 
 !!! note
 
-    The default settings that will always be loaded are in [eligibility_server/settings.py](https://github.com/cal-itp/eligibility-server/blob/dev/eligibility_server/settings.py)
+    The default settings that will always be loaded are in [eligibility_server/settings.py](https://github.com/cal-itp/eligibility-server/blob/main/eligibility_server/settings.py)
 
 ## Creating a new keypair
 

docs/deployment/infrastructure.md

@@ -86,7 +86,7 @@ Docker logs can be viewed in the Advanced Tools for the instance. The URL patter
 
 ## Making changes
 
-Terraform is [`plan`](https://www.terraform.io/cli/commands/plan)'d when code is pushed to any branch on GitHub, then [`apply`](https://www.terraform.io/cli/commands/apply)'d when merged to `dev`. While other automation for this project is done through GitHub Actions, we use an Azure Pipeline (above) for a couple of reasons:
+Terraform is [`plan`](https://www.terraform.io/cli/commands/plan)'d when code is pushed to any branch on GitHub, then [`apply`](https://www.terraform.io/cli/commands/apply)'d when merged to `main`. While other automation for this project is done through GitHub Actions, we use an Azure Pipeline (above) for a couple of reasons:
 
 - Easier authentication with the Azure API using a service connnection
 - Log output is hidden, avoiding accidentally leaking secrets

docs/getting-started.md

@@ -71,7 +71,7 @@ Starting the Dev Container will run `bin/init.sh`, which runs a command to initi
 
 ### Run unit tests
 
-Unit tests are implemented with [`pytest`](https://docs.pytest.org/en/6.2.x/) and can be found in the [`tests/`](https://github.com/cal-itp/eligibility-server/tree/dev/tests) directory in the repository. `pytest` is installed and available to run directly in the devcontainer.
+Unit tests are implemented with [`pytest`](https://docs.pytest.org/en/6.2.x/) and can be found in the [`tests/`](https://github.com/cal-itp/eligibility-server/tree/main/tests) directory in the repository. `pytest` is installed and available to run directly in the devcontainer.
 
 The test suite runs against every pull request via a GitHub Action.
 

docs/releases.md

@@ -2,14 +2,14 @@
 
 The `eligibility-server` is published as a Docker image on the GitHub Container Registry. It can be accessed from the [repository package page](https://github.com/cal-itp/eligibility-server/pkgs/container/eligibility-server).
 
-Every push to the `dev` (default) branch that changes files relevant to the application builds and updates the `dev` package, via the [`docker-publish`](https://github.com/cal-itp/eligibility-server/blob/dev/.github/workflows/docker-publish.yml) GitHub Action.
+Every push to the `main` (default) branch that changes files relevant to the application builds and updates the `dev` package, via the [`docker-publish`](https://github.com/cal-itp/eligibility-server/blob/main/.github/workflows/docker-publish.yml) GitHub Action.
 
 Every release created also pushes a new package publication.
 
 ## Versions
 
 All versions of the package may be viewed on the [package all versions page](https://github.com/cal-itp/eligibility-server/pkgs/container/eligibility-server/versions).
 
-The `dev` (default) branch is published at the `dev` tag:
+The `main` (default) branch is published at the `dev` tag:
 
-The official releases will be tagged with a version number and the `latest` tag.
+The official releases will be tagged with a version number and their respective environment (`test`, `prod`) tag.

mkdocs.yml

@@ -1,7 +1,7 @@
 site_name: "cal-itp/eligibility-server: documentation"
 site_url: https://docs.calitp.org/eligibility-server
 repo_url: https://github.com/cal-itp/eligibility-server
-edit_uri: edit/dev/docs
+edit_uri: edit/main/docs
 
 theme:
   name: material