Fix publish docs workflow #58
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
UncleGrumpy
force-pushed
the
publish_docs
branch
2 times, most recently
from
9e233c7 to
def0e3c
Compare
UncleGrumpy
had a problem deploying
to
github-pages
GitHub Actions
Failure
UncleGrumpy
force-pushed
the
publish_docs
branch
2 times, most recently
from
c153b9e to
836fdf0
Compare
UncleGrumpy
had a problem deploying
to
github-pages
GitHub Actions
Failure
Updates publish_docs.yml to run on pull requests and pushes. In personal forks configure-pages action and the deploy job are skipped so the workflow can succeed. The publish job is only run on pushes to the atomvm/atomvm_rebar3_plugin master branch. Signed-off-by: Winford <[email protected]>
UncleGrumpy
force-pushed
the
publish_docs
branch
from
836fdf0 to
68e1fa1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Updates publish_docs.yml to run on pull requests and pushes. In personal forks configure-pages action and the deploy job are skipped so the workflow can succeed. The publish job is only run on pushes to the atomvm/atomvm_rebar3_plugin master branch.