Change all references of master to main

Author: irvingpop

.github/SETUP.md

@@ -39,18 +39,18 @@ After adding the secret, the workflow will automatically:
 - Authenticate to AWS using OIDC (no credentials stored)
 - Build Docker images for ARM64 platform
 - Push to ECR with appropriate tags:
-  - `:staging` for non-master branches
-  - `:prod` for master branch (after CI passes)
+  - `:staging` for non-main branches
+  - `:prod` for main branch (after CI passes)
 
 ## Testing
 
 To test the setup:
 
-1. **Test staging build**: Push to any branch except `master`
+1. **Test staging build**: Push to any branch except `main`
    - Should trigger Docker build and push to `:staging` tag
    - Check ECR repository to verify image was pushed
 
-2. **Test production build**: Merge to `master` branch
+2. **Test production build**: Merge to `main` branch
    - Should run lint, test, security checks first
    - If all pass, should build and push to `:prod` tag
    - Check ECR repository to verify image was pushed

.github/workflows/ci.yml

@@ -2,9 +2,9 @@ name: CI
 
 on:
   push:
-    branches: [master]
+    branches: [main]
   pull_request:
-    branches: [master]
+    branches: [main]
 
 env:
   POETRY_VERSION: "2.3.0"
@@ -14,8 +14,8 @@ jobs:
   lint:
     name: Lint
     runs-on: ubuntu-latest
-    # Only run on master branch pushes and PRs to master
-    if: github.event_name == 'pull_request' || github.ref == 'refs/heads/master'
+    # Only run on main branch pushes and PRs to main
+    if: github.event_name == 'pull_request' || github.ref == 'refs/heads/main'
     steps:
       - name: Checkout code
         uses: actions/checkout@v4
@@ -62,8 +62,8 @@ jobs:
   test:
     name: Test
     runs-on: ubuntu-latest
-    # Only run on master branch pushes and PRs to master
-    if: github.event_name == 'pull_request' || github.ref == 'refs/heads/master'
+    # Only run on main branch pushes and PRs to main
+    if: github.event_name == 'pull_request' || github.ref == 'refs/heads/main'
     steps:
       - name: Checkout code
         uses: actions/checkout@v4
@@ -125,8 +125,8 @@ jobs:
   security:
     name: Security Scan
     runs-on: ubuntu-latest
-    # Only run on master branch pushes and PRs to master
-    if: github.event_name == 'pull_request' || github.ref == 'refs/heads/master'
+    # Only run on main branch pushes and PRs to main
+    if: github.event_name == 'pull_request' || github.ref == 'refs/heads/main'
     steps:
       - name: Checkout code
         uses: actions/checkout@v4
@@ -173,9 +173,9 @@ jobs:
   docker-build-push:
     name: Build and Push Docker Image
     runs-on: ubuntu-latest
-    # Run on push to master (build+push) and on PRs (build only)
+    # Run on push to main (build+push) and on PRs (build only)
     if: github.event_name == 'push' || github.event_name == 'pull_request'
-    # For master/PR, wait for CI checks to pass
+    # For main/PR, wait for CI checks to pass
     needs: [ci-success]
     permissions:
       id-token: write  # Required for OIDC authentication
@@ -232,7 +232,7 @@ jobs:
       - name: Determine Docker tag
         id: docker-tag
         run: |
-          if [ "${{ github.ref }}" == "refs/heads/master" ]; then
+          if [ "${{ github.ref }}" == "refs/heads/main" ]; then
             echo "image=633607774026.dkr.ecr.us-east-2.amazonaws.com/back-end:prod" >> $GITHUB_OUTPUT
             echo "environment=Production" >> $GITHUB_OUTPUT
           else
@@ -286,20 +286,20 @@ jobs:
     # Always run to satisfy docker-build-push dependency
     if: always()
     steps:
-      - name: Check all jobs passed (master/PR only)
-        if: github.event_name == 'pull_request' || github.ref == 'refs/heads/master'
+      - name: Check all jobs passed (main/PR only)
+        if: github.event_name == 'pull_request' || github.ref == 'refs/heads/main'
         run: |
-          # Check if jobs were skipped (non-master) or failed
+          # Check if jobs were skipped (non-main) or failed
           if [[ "${{ needs.lint.result }}" == "skipped" ]]; then
-            echo "Lint job was skipped - this should not happen on master/PR"
+            echo "Lint job was skipped - this should not happen on main/PR"
             exit 1
           fi
           if [[ "${{ needs.lint.result }}" != "success" ]]; then
             echo "Lint job failed"
             exit 1
           fi
           if [[ "${{ needs.test.result }}" == "skipped" ]]; then
-            echo "Test job was skipped - this should not happen on master/PR"
+            echo "Test job was skipped - this should not happen on main/PR"
             exit 1
           fi
           if [[ "${{ needs.test.result }}" != "success" ]]; then
@@ -308,7 +308,7 @@ jobs:
           fi
           # Security is informational, doesn't fail CI
           echo "All required jobs passed!"
-      - name: Pass through for non-master branches
-        if: github.event_name != 'pull_request' && github.ref != 'refs/heads/master'
+      - name: Pass through for non-main branches
+        if: github.event_name != 'pull_request' && github.ref != 'refs/heads/main'
         run: |
-          echo "Skipping CI checks for non-master branch (staging build will proceed)"
+          echo "Skipping CI checks for non-main branch (staging build will proceed)"

CONTRIBUTING.md

@@ -172,7 +172,7 @@ High level overview of upcoming Operation Code goals.  This is the source of upc
 
 ## Working On Your Issue
 
-* Please first **read** Operation Code's [guidelines for working an issue](https://github.com/OperationCode/operationcode/blob/master/CONTRIBUTING.md#guidelines-for-working-an-issue)
+* Please first **read** Operation Code's [guidelines for working an issue](https://github.com/OperationCode/operationcode/blob/main/CONTRIBUTING.md#guidelines-for-working-an-issue)
 
 * From the forked and cloned repository on your environment, you can now create a [feature branch](http://nvie.com/posts/a-successful-git-branching-model/). It is a good idea to name your branch after the issue it is attached to.
 
@@ -188,10 +188,10 @@ git branch
 
 * Once you have finished your work, head over to **Operation Code**'s main GitHub page, and make a pull request. More information about pull requests can be found in the next section.
 
-* To return to your main `master` branch, type the following in the terminal:
+* To return to your main `main` branch, type the following in the terminal:
 
 ```bash
-git checkout master
+git checkout main
 ```
 
 </details>
@@ -202,10 +202,10 @@ git checkout master
   <summary>Click to Expand</summary>
 Some issues take awhile to code a solution for. It is very normal to take a large amount of time to turn in 
 well-written work that resolves an issue! In the meantime, there could be many other people contributing to the 
-code base. Since we use Git, you'll want to keep you project up-to-date with the `master` branch so there are no 
+code base. Since we use Git, you'll want to keep you project up-to-date with the `main` branch so there are no 
 [merge conflicts](https://help.github.com/articles/about-merge-conflicts/) to resolve when you make your pull request.
 <ol>
-  <li> <a href="https://help.github.com/articles/syncing-a-fork/">Keep your fork in sync with Operation Code's master branch.</a></li>
+  <li> <a href="https://help.github.com/articles/syncing-a-fork/">Keep your fork in sync with Operation Code's main branch.</a></li>
 </ol>
 </details>
 
@@ -291,7 +291,7 @@ Download and install Git for Windows from https://git-scm.com/download/win
 
 Download the latest version of python at https://www.python.org/downloads/, (3.7.3 at time of writing)
 
-Follow the steps found in the [Quick Start Guide](https://github.com/OperationCode/back-end/blob/master/README.md#quick-start)
+Follow the steps found in the [Quick Start Guide](https://github.com/OperationCode/back-end/blob/main/README.md#quick-start)
 
 Occasionally you will deal with path issues this is fixed within windows by adding the appropriate key value pair to the path.
 

MAINTAINERS.md

@@ -2,7 +2,7 @@
 
 This file lists how the Operation Code Back End project is maintained. When making changes to the system, this file tells you who needs to review your contribution - you need a simple majority of maintainers for the relevant subsystems to provide a 👍 on your pull request. Additionally, you need to not receive a veto from a lieutenant or the project lead.
 
-Check out [how Operation Code Open Source projects are maintained](https://github.com/OperationCode/START_HERE/blob/master/open_source_maintenance_policy.md) for details on the process, how to become a maintainer, lieutenant, or the project lead.
+Check out [how Operation Code Open Source projects are maintained](https://github.com/OperationCode/START_HERE/blob/main/open_source_maintenance_policy.md) for details on the process, how to become a maintainer, lieutenant, or the project lead.
 
 # Project Lead
 

OPS.md

@@ -8,8 +8,8 @@ The backend is deployed to AWS ECS (Elastic Container Service) with separate sta
 
 Docker images are automatically built and pushed to AWS ECR via GitHub Actions:
 
-- **PR branches** (any branch except `master`): Automatically builds and pushes to `:staging` tag
-- **Master branch**: Automatically builds and pushes to `:prod` tag after CI checks pass
+- **PR branches** (any branch except `main`): Automatically builds and pushes to `:staging` tag
+- **main branch**: Automatically builds and pushes to `:prod` tag after CI checks pass
 
 The automated builds use AWS OIDC for secure authentication (no long-lived credentials).
 
@@ -208,8 +208,8 @@ After setup, the GitHub Actions workflow will automatically:
 - Push images to ECR with appropriate tags (`:staging` or `:prod`)
 
 You can verify by:
-1. Pushing a commit to a non-master branch (should push `:staging`)
-2. Merging to master (should push `:prod` after tests pass)
+1. Pushing a commit to a non-main branch (should push `:staging`)
+2. Merging to main (should push `:prod` after tests pass)
 3. Checking ECR repository for new images
 
 ## Security Best Practices

src/gunicorn_config.py

@@ -48,7 +48,7 @@
 #
 #       A positive integer generally set to around 1000.
 #
-#   timeout - If a worker does not notify the master process in this
+#   timeout - If a worker does not notify the main process in this
 #       number of seconds it is killed and a new worker is spawned
 #       to replace it.
 #
@@ -73,7 +73,7 @@
 
 #   preload_app - Load application code before forking worker processes.
 #       This conserves memory and speeds up server boot times by loading
-#       the Django application once in the master process, then forking
+#       the Django application once in the main process, then forking
 #       worker processes with shared code in memory.
 #
 #       Greatly improves startup performance by eliminating redundant
@@ -186,7 +186,7 @@
 #       A callable that accepts the same arguments as after_fork
 #
 #   pre_exec - Called just prior to forking off a secondary
-#       master process during things like config reloading.
+#       main process during things like config reloading.
 #
 #       A callable that takes a server instance as the sole argument.
 #