Better documentation build workflow from 2021 GA Hackathon #1987
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.
Description
This is the documentation workflow I submitted to the 2021 GitHub Actions Hackathon.
It was designed to mimic ReadTheDocs behavior as much as possible. In this PR I present a simplified version, more suitable for TARDIS (since we are not going to use things like deploying SemVer tags, for example) and easier to understand.
Consists of two different workflows:
build_docs.yml
andclean_docs.yml
.Usage
Once merged, we can expect the following behavior:
master
will result in a new build of https://tardis-sn.github.io/tardislatest
could be changed to any word we want. Originally the wordstable
was reserved for the latest SemVer tag.build-docs
. Requires at leasttriage
permissions.push
trigger are deployed under https://tardis-sn.github.io/tardis/branch/branch-namegh-pages
branch tidy.Motivation and context
A better/easier to understand documentation pipeline.
How has this been tested?
Except for some minor details regarding to the TARDIS-specific implementation, these workflows were extensively tested since November 2021.
Notice this workflow uses the
pull_request_target
and this trigger can't be tested from this PR. Requires merging to see if it's working. You can see successful branch builds on my fork and a pull request example.Examples
Type of change
Checklist