Skip to content

Commit

Permalink
Replace more Master with Main
Browse files Browse the repository at this point in the history
Replace more references to the `master` branch with references to the `main` branch, as per recent and new standard for new repositories by GitHub.
  • Loading branch information
HumbleDeer committed May 1, 2024
1 parent 492e1ee commit afc4c56
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/user-guide/deploying-your-docs.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ which require a different work flow when deploying.

Project Pages sites are simpler as the site files get deployed to a branch
within the project repository (`gh-pages` by default). After you `checkout` the
primary working branch (usually `master`) of the git repository where you
primary working branch (usually `main`) of the git repository where you
maintain the source documentation for your project, run the following command:

```sh
Expand Down Expand Up @@ -49,7 +49,7 @@ If there are untracked files or uncommitted work in the local repository where
### User and Organisation Pages

User and Organization GitHub Pages sites are not tied to a specific project,
and the site files are deployed to the `master` branch in a dedicated
and the site files are deployed to the `main` branch in a dedicated
repository named with the GitHub account name. Therefore, you will need working
copies of two repositories on your local system. For example, consider the
following file structure:
Expand Down

0 comments on commit afc4c56

Please sign in to comment.