Clean build process #58
Conversation
Command run: scripts/add-all-cc-repos-as-submodules
…add as submodules
|
@ribose-jeffreylau for your follow up. I'm not sure why your merged commits in #55 is showing up here...? |
I think I pushed my PR into main by mistake, when I thought I was pushing to the PR branch. For context, locally, I just set it up to remote-track Staging's |
ribose-jeffreylau
force-pushed
the
rt-clean-processing
branch
from
5b868a9 to
d84dc67
Compare
ronaldtse
had a problem deploying
to
github-pages
GitHub Actions
Failure
|
@ribose-jeffreylau the aggregation step isn't correct yet, need your help to fix: It's downloading all the artifacts but seem to not be merging correctly. |
|
There are other issues apart from this. Paths to documents need adjustment, which I'm fixing now. |
... Still needed for the scaffolding.
... to repopulate `metanorma.source.files` array of a target YAML, given a doc type, a document class, and a sub-directory from which to search documents.
Command run: DOC_TYPE=administrative DOC_CLASS=cc scripts/repopulate-metanorma-yaml src-documents metanorma-admin.yml
Command run: DOC_TYPE=standard DOC_CLASS=cc scripts/repopulate-metanorma-yaml src-documents metanorma-standards.yml
This reverts commit b6edba7. Too many changes to deal with at a time. Reverting.
This reverts commit 73c444d.
This reverts commit 6a01bcf.
This reverts commit dbdba45.
This reverts commit 7732dad.
... to get around limitation of not being able to output to ../_site/...
…with src-documents again ... to prepare for adjustments in the GHA build_deploy workflow.
…ion} to expect to be run from repo root These two doc types are expected to be managed manually, from the fact that the document IDs were hard-coded into the original adoc pages.
This reverts commit 0022656.
ribose-jeffreylau
force-pushed
the
rt-clean-processing
branch
from
4675923 to
8213734
Compare
|
@ronaldtse It should be ready for review. |
|
Thank you @ribose-jeffreylau ! Finally we're done! |
No description provided.