dan
/
jekyll
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Replace references to 'master' branch with 'main' (#8657) 

As the default branch name on GitHub has been `main` for a while now: https://github.blog/changelog/2020-10-01-the-default-branch-for-newly-created-repositories-is-now-main/
This commit is contained in:
Jesse van der Pluijm 2021-05-14 21:05:40 +02:00 committed by GitHub
parent 62ba3c03b7
commit c523f041fc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/_docs/continuous-integration/github-actions.md
View File

@ -30,8 +30,8 @@ The first and foremost requirement is a Jekyll project hosted at GitHub. Choose
project or follow the [quickstart]({{ '/docs/' | relative_url }}) and push the repository to GitHub project or follow the [quickstart]({{ '/docs/' | relative_url }}) and push the repository to GitHub
if it is not hosted there already. if it is not hosted there already.
We're only going to cover builds from the `master` branch in this page. Therefore, ensure that you We're only going to cover builds from the `main` branch in this page. Therefore, ensure that you
are working on the `master` branch. If necessary, you may create it based on your default branch. are working on the `main` branch. If necessary, you may create it based on your default branch.
When the Action builds your site, the contents of the _destination_ directory will be automatically When the Action builds your site, the contents of the _destination_ directory will be automatically
pushed to the `gh-pages` branch with a commit, ready to be used for serving. pushed to the `gh-pages` branch with a commit, ready to be used for serving.
@ -106,7 +106,7 @@ name: Build and deploy Jekyll site to GitHub Pages
on: on:
push: push:
branches: branches:
- master - main
jobs: jobs:
github-pages: github-pages:
@ -122,7 +122,7 @@ jobs:
The above workflow can be explained as the following: The above workflow can be explained as the following:
- We trigger the build using **on.push** condition for `master` branch only --- this prevents - We trigger the build using **on.push** condition for `main` branch only --- this prevents
the Action from overwriting the `gh-pages` branch on any feature branch pushes. the Action from overwriting the `gh-pages` branch on any feature branch pushes.
- The **name** of the job matches our YAML filename: `github-pages`. - The **name** of the job matches our YAML filename: `github-pages`.
- The **checkout** action takes care of cloning your repository. - The **checkout** action takes care of cloning your repository.