mirror of
https://github.com/JamesIves/github-pages-deploy-action.git
synced 2023-12-15 20:03:39 +08:00
CNAME
This commit is contained in:
parent
292d54d98b
commit
7546e3a187
@ -57,6 +57,7 @@ The `secrets` and `env` portion of the workflow **must** be configured before th
|
|||||||
| `BUILD_SCRIPT` | If you require a build script to compile your code prior to pushing it you can add the script here. The Docker container which powers the action runs Node which means `npm` commands are valid. If you're using a static site generator such as Jekyll I'd suggest compiling the code prior to pushing it to your base branch. | `env` | **No** |
|
| `BUILD_SCRIPT` | If you require a build script to compile your code prior to pushing it you can add the script here. The Docker container which powers the action runs Node which means `npm` commands are valid. If you're using a static site generator such as Jekyll I'd suggest compiling the code prior to pushing it to your base branch. | `env` | **No** |
|
||||||
| `COMMIT_NAME` | Used to sign the commit, this should be your name. If not provided it will default to `username@users.noreply.github.com` | `env` | **No** |
|
| `COMMIT_NAME` | Used to sign the commit, this should be your name. If not provided it will default to `username@users.noreply.github.com` | `env` | **No** |
|
||||||
| `COMMIT_EMAIL` | Used to sign the commit, this should be your email. If not provided it will default to your username. | `env` | **No** |
|
| `COMMIT_EMAIL` | Used to sign the commit, this should be your email. If not provided it will default to your username. | `env` | **No** |
|
||||||
|
| `CNAME` | If you're using a custom domain, you will need to add the domain name to the `CNAME` environment variable. If you don't do this GitHub will wipe out your domain configuration after each deploy. This value will look something like this: `jamesives.dev`. | `env` | **No** |
|
||||||
|
|
||||||
With the action correctly configured you should see something similar to this in your GitHub actions workflow editor.
|
With the action correctly configured you should see something similar to this in your GitHub actions workflow editor.
|
||||||
|
|
||||||
|
@ -64,9 +64,15 @@ git checkout "${BASE_BRANCH:-master}" && \
|
|||||||
echo "Running build scripts... $BUILD_SCRIPT" && \
|
echo "Running build scripts... $BUILD_SCRIPT" && \
|
||||||
eval "$BUILD_SCRIPT" && \
|
eval "$BUILD_SCRIPT" && \
|
||||||
|
|
||||||
|
if [ "$CNAME" ]; then
|
||||||
|
echo "Generating a CNAME file in in the $FOLDER directory."
|
||||||
|
echo $CNAME > $FOLDER/CNAME
|
||||||
|
fi
|
||||||
|
|
||||||
# Commits the data to Github.
|
# Commits the data to Github.
|
||||||
echo "Deploying to GitHub..." && \
|
echo "Deploying to GitHub..." && \
|
||||||
git add -f $FOLDER && \
|
git add -f $FOLDER && \
|
||||||
|
|
||||||
git commit -m "Deploying to ${BRANCH} - $(date +"%T")" && \
|
git commit -m "Deploying to ${BRANCH} - $(date +"%T")" && \
|
||||||
git push $REPOSITORY_PATH `git subtree split --prefix $FOLDER master`:$BRANCH --force && \
|
git push $REPOSITORY_PATH `git subtree split --prefix $FOLDER master`:$BRANCH --force && \
|
||||||
echo "Deployment succesful!"
|
echo "Deployment succesful!"
|
Loading…
Reference in New Issue
Block a user