Closed pconrad closed 3 years ago
Merging #171 (4db1968) into main (3e33145) will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## main #171 +/- ##
=========================================
Coverage 99.82% 99.82%
Complexity 342 342
=========================================
Files 83 83
Lines 1669 1669
Branches 77 77
=========================================
Hits 1666 1666
Misses 3 3
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 3e33145...4db1968. Read the comment docs.
In this PR, we set up a GitHub workflow to publish the storybook for the repo.
The storybook is published on GitHub pages in two separate repos:
One of the workflows is set up to publish to the production site, i.e. https://ucsb-cs156-s21.github.io/proj-ucsb-cs-las-docs, only on a push to the main branch (i.e. when a PR is merged.)
The other workflow is set up to publish to the QA branch any time there is a PR. Note the implications: if there are multiple PRs outstanding, the contents of the qa GitHub pages site will always reflect the most recent PR that was made. Teams will have to coordinate in order to review changes to the Storybook, so this is not a perfect solution. But it at least guarantees that if there are any problems with the publishing, those will get flagged as CI/CD errors, and it encourages teams to review the storybook before merging a PR.
The other sites need to be set up as follows:
First, add a file under
docs/index.md
that looks like this for the production docs site:And like this for the qa docs site:
Then, you can go to
Settings
for each of these repos, thenPages
(near bottom of left nav) to enable GitHub Pages on themain
branch and the/docs
subdirectory.It is also necessary to set up a Personal Access Token called
TOKEN
with scoperepo
and add it to the repository secrets.