Rename master to main.

Author: tillahoffmann

.github/PULL_REQUEST_TEMPLATE/new_container.md

@@ -4,5 +4,5 @@ You have implemented a new container and would like to contribute it? Great! Her
 - [ ] Implement the new feature (typically in `__init__.py`) and corresponding tests.
 - [ ] Add a line `-e file:[feature name]` to `requirements.in` and run `make requirements`. This command will find any new requirements and generate lock files to ensure reproducible builds (see the [pip-tools documentation](https://pip-tools.readthedocs.io/en/latest/) for details). Then run `pip install -r requirements/[your python version].txt` to install the new requirements.
 - [ ] Update the feature `README.rst` and add it to the table of contents (`toctree` directive) in the top-level `README.rst`.
-- [ ] Add a line `[feature name]` to the list of components in the  GitHub Action workflow in `.github/workflows/main.yml` to run tests, build, and publish your package when pushed to the `master` branch.
-- [ ] Rebase your development branch on `master` (or merge `master` into your development branch).
+- [ ] Add a line `[feature name]` to the list of components in the  GitHub Action workflow in `.github/workflows/main.yml` to run tests, build, and publish your package when pushed to the `main` branch.
+- [ ] Rebase your development branch on `main` (or merge `main` into your development branch).

.github/workflows/docs.yml

@@ -1,9 +1,9 @@
 name: testcontainers documentation
 on:
   push:
-    branches: [master]
+    branches: [main]
   pull_request:
-    branches: [master]
+    branches: [main]
 
 jobs:
   build:

.github/workflows/main.yml

@@ -1,9 +1,9 @@
 name: testcontainers packages
 on:
   push:
-    branches: [master]
+    branches: [main]
   pull_request:
-    branches: [master]
+    branches: [main]
 
 jobs:
   build:
@@ -76,7 +76,7 @@ jobs:
       - name: Upload the package to pypi
         if: >
           github.event_name == 'push'
-          && github.ref == 'refs/heads/master'
+          && github.ref == 'refs/heads/main'
           && github.repository_owner == 'testcontainers'
           && matrix.python-version == '3.10'
         env:

.github/workflows/requirements.yml

@@ -1,9 +1,9 @@
 name: testcontainers requirements
 on:
   push:
-    branches: [master]
+    branches: [main]
   pull_request:
-    branches: [master]
+    branches: [main]
 
 jobs:
   requirements:

README.rst

@@ -114,5 +114,5 @@ You want to contribute a new feature or container? Great! You can do that in six
 2. Implement the new feature (typically in :code:`__init__.py`) and corresponding tests.
 3. Add a line :code:`-e file:[feature name]` to :code:`requirements.in` and run :code:`make requirements`. This command will find any new requirements and generate lock files to ensure reproducible builds (see the `pip-tools <https://pip-tools.readthedocs.io/en/latest/>`__ documentation for details). Then run :code:`pip install -r requirements/[your python version].txt` to install the new requirements.
 4. Update the feature :code:`README.rst` and add it to the table of contents (:code:`toctree` directive) in the top-level :code:`README.rst`.
-5. Add a line :code:`[feature name]` to the list of components in the  GitHub Action workflow in :code:`.github/workflows/main.yml` to run tests, build, and publish your package when pushed to the :code:`master` branch.
-6. Rebase your development branch on :code:`master` (or merge :code:`master` into your development branch).
+5. Add a line :code:`[feature name]` to the list of components in the  GitHub Action workflow in :code:`.github/workflows/main.yml` to run tests, build, and publish your package when pushed to the :code:`main` branch.
+6. Rebase your development branch on :code:`main` (or merge :code:`main` into your development branch).