CI: stop triggering CircleCI on automated pushes to gh-pages #151
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed how there were failing builds in CircleCI. They were triggered by pushes to gh-pages, and complained that there were no .circleci/config.yml in there (in the gh-pages branch).
When I was trying to create a stub it required me to define a lot to not fail validation. So, instead I opt to disable the build by adding a "[skip ci]" within the commit message for the gh-pages branch made by the
ghp-import
CLI.