Skip to content

Commit 54287c5

Browse files
authored
docs: adjust placement
1 parent be62bf6 commit 54287c5

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

README.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -80,6 +80,9 @@ jobs:
8080
folder: build # The folder the action should deploy.
8181
```
8282
83+
> [!NOTE]
84+
> You must configure your repository to deploy from the branch you push to. To do this, go to your repository settings, click on `Pages`, and choose `Deploy from a Branch` from the `Source` dropdown. From there select the branch you supplied to the action, in most cases this will be `gh-pages` as that's the default.
85+
8386
If you'd like to make it so the workflow only triggers on push events to specific branches then you can modify the `on` section.
8487

8588
```yml
@@ -97,10 +100,6 @@ permissions:
97100
contents: write
98101
```
99102

100-
101-
> [!NOTE]
102-
> You must configure your repository to deploy from the branch you push to. To do this, go to your repository settings, click on `Pages`, and choose `Deploy from a Branch` from the `Source` dropdown. From there select the branch you supplied to the action, in most cases this will be `gh-pages` as that's the default.
103-
104103
## Configuration 📁
105104

106105
The `with` portion of the workflow **must** be configured before the action will work. You can add these in the `with` section found in the examples above. Any `secrets` must be referenced using the bracket syntax and stored in the GitHub repository's `Settings/Secrets` menu. You can learn more about setting environment variables with GitHub actions [here](https://help.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets).

0 commit comments

Comments
 (0)