You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generates DocC documentation from Swift Bitcoin's repo and deploy to `/docs` path of the organization's [website](https://swift-bitcoin.github.io/).
3
+
Generates DocC documentation from Swift Bitcoin's repo and deploy to [/docs](https://swift-bitcoin.github.io/docs/documentation/bitcoin) path of the organization's website.
4
4
5
5
## Why separate repo?
6
6
7
-
Because it's easy to checkout Repo B (e.g. `swift-bitcoin` repo) from a GH Action running on Repo A (e.g. this repo) and later deploy to repo A's GH Pages. But it is not at all possible to run an action on Repo B and have it deploy artifacts another repo/org's GH pages.
7
+
Because it's simple enough to checkout Repo B (e.g. `swift-bitcoin` repo) from a GitHub Action running on Repo A (e.g. this repo) and deploy the generated docs to Repo A's GitHub Pages URL while it is not at all possible to run an Action directly on Repo B and have it deploy the docs artifacts to a different repo's Pages URL (or to the organization's Pages URL).
8
8
9
-
Having a standalone docs repo with Pages will create the subfolder needed to host the documentation pages generated independently from the main site/blog.
9
+
Having a standalone docs repo with Pages on will also create the subfolder needed (in this case _docs_) to host the documentation pages generated independently from the main site and blog.
0 commit comments