If you would rather use a deploy key instead of a personal access token, you can by starting with the Circle CI instructions for adding a read/write deploy key.
When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a new file, .circleci/config.yml, in your gh-pages branch with the following contents:
When initially deploying to a gh-pages branch using Circle CI, you may notice that some jobs triggered by commits to the gh-pages branch fail to run successfully due to a lack of tests. You can easily work around this by creating a basic Circle CI config with the following contents:
# Circle CI 2.0 Config File
# This config file will prevent tests from being run on the gh-pages branch.
version: 2
@@ -109,7 +109,7 @@ deployment:
steps:
-run: echo "Skipping tests on gh-pages branch"
Once you commit and push this file to your remote gh-pages branch on GitHub, Circle will skip running tests on the gh-pages branch.
Save this file as config.yml and place it in a .circleci folder inside your website/assets folder.