doc: rename master branch to main (#9022)

docs/_index.md

@@ -85,7 +85,7 @@ Finally, `pipx` can install any valid [pip requirement spec](https://pip.pypa.io
 allows for installations of the development version from `git`, or even for local testing of pull requests:
 
 ```bash
-pipx install --suffix @master git+https://github.com/python-poetry/poetry.git@master
+pipx install --suffix @main git+https://github.com/python-poetry/poetry.git@main
 pipx install --suffix @pr1234 git+https://github.com/python-poetry/poetry.git@refs/pull/1234/head
 ```
 
@@ -182,7 +182,7 @@ curl -sSL https://install.python-poetry.org | POETRY_VERSION=1.2.0 python3 -
 You can also install Poetry from a `git` repository by using the `--git` option:
 
 ```bash
-curl -sSL https://install.python-poetry.org | python3 - --git https://github.com/python-poetry/poetry.git@master
+curl -sSL https://install.python-poetry.org | python3 - --git https://github.com/python-poetry/poetry.git@main
 ````
 If you want to install different versions of Poetry in parallel, a good approach is the installation with pipx and suffix.
 

docs/contributing.md

@@ -191,7 +191,7 @@ base branch. A maintainer might ask you to ensure the branch is up-to-date prior
 (especially if there have been CI changes on the base branch), and will also ask you to fix any conflicts.
 {{% /note %}}
 
-All pull requests, unless otherwise instructed, need to be first accepted into the `master` branch. Maintainers will
+All pull requests, unless otherwise instructed, need to be first accepted into the `main` branch. Maintainers will
 generally decide if any backports to other branches are required, and carry them out as needed.
 
 ### Issue triage
@@ -233,15 +233,15 @@ When trying to reproduce issues, you often want to use multiple versions of Poet
 ```sh
 pipx install --suffix @1.2.1 'poetry==1.2.1'
 pipx install --suffix @1.3.0rc1 'poetry==1.3.0rc1'
-pipx install --suffix @master 'poetry @ git+https://github.com/python-poetry/poetry'
+pipx install --suffix @main 'poetry @ git+https://github.com/python-poetry/poetry'
 pipx install --suffix @local '/path/to/local/clone/of/poetry'
 
 # now you can use any of the chosen versions of Poetry with their configured suffix, e.g.
-poetry@master --version
+poetry@main --version
 ```
 
 {{% note %}}
-Do not forget to `pipx upgrade poetry@master` before using it, to make sure you have the latest changes.
+Do not forget to `pipx upgrade poetry@main` before using it, to make sure you have the latest changes.
 {{% /note %}}
 
 {{% note %}}

docs/dependency-specification.md

@@ -132,7 +132,7 @@ requests = { git = "https://github.com/requests/requests.git" }
 ```
 
 Since we haven’t specified any other information,
-Poetry assumes that we intend to use the latest commit on the `master` branch
+Poetry assumes that we intend to use the latest commit on the `main` branch
 to build our project.
 
 You can combine the `git` key with the `branch` key to use another branch.

docs/plugins.md

@@ -263,7 +263,7 @@ removing them, sometimes the signature of an internal method has to be changed.
 As the author of a plugin, you are probably testing your plugin
 against the latest release of Poetry.
 Additionally, you should consider testing against the latest release branch and the
-master branch of Poetry and schedule a CI job that runs regularly even if you did not
+main branch of Poetry and schedule a CI job that runs regularly even if you did not
 make any changes to your plugin.
 This way, you will notice internal changes that break your plugin immediately
 and can prepare for the next Poetry release.