FAQ
Question
Explain these GitHub workflows yaml files?¶
dev.yml
: define dev workflow, run on every push and pull requests to master, basically run all the tests against multiple versions and platforms.preview.yml
: define stage & preview workflow, run on every push to master, publish dev build to TestPyPI.release.yml
: define release & publish workflow, run on every tag push, create GitHub release, publish docs to GitHub Pages and built package to PyPI.
Question
Why not travis CI?¶
Travis CI is a great service, however, github actions is super convenient, less configuration , better integration. Less configuration, less error prone.
Question
Why not read the docs?¶
Same reason as above. GitHub Pages is convenient than read the docs, it requires no further configuration, except access token. As to read the docs, you need to write v2 config file, plus several settings on web pages.
Question
Why mkdocs over sphinx?¶
reStructured Text and Sphinx is way to tedious, though powerful. With extension, you'll find almost all features are available in mkdocs, in a neat and productive way. Poetry and Markdown, are the two key factors driven me develop this template.
Question
What are the configuration items?¶
Here is a list:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 |
|
except above settings, for CI/CD, you'll also need configure gitub repsitory secrets at page repo > settings > secrtes, and add the following secrets:
- PERSONAL_TOKEN (required for publishing document to git pages)
- TEST_PYPI_API_TOKEN (required for publishing dev release to testpypi)
- PYPI_API_TOKEN (required for publish )