Closed bitjammer closed 2 years ago
Hi @bitjammer, can I work on this? I went through the mentioned PR and I now have a clear idea on what needs to be done.
Of course, that’s why it’s here! Thank you for taking it on. Please have a go and let me know if you have any questions.
Hi @bitjammer, I raised a PR. I used the approach to use an env variable. Hope that's fine.
Hi @bitjammer, just sending a little nudge to bump up the PR in your inbox. Thanks.
Thank you! I will have a look at this today.
Nice work @A-N-uraag, thank you.
From https://github.com/apple/swift-docc-plugin/pull/21#discussion_r929419898
In some scenarios, running swift-docc-plugin tests against the built-in docc in the installed toolchain could save time. Add an option to
./bin/test
to skip cloningswift-docc
andswift-docc-render-artifact
and setting the environment variables to use those.Behavior:
If
--skip-building-upstream-docc
(or perhaps an environment variable) is set:SWIFT_DOCC_ROOT
SWIFT_DOCC_RENDER_ARTIFACT_ROOT
SWIFT_DOCC_BRANCH
SWIFT_DOCC_RENDER_ARTIFACT_BRANCH
swift-docc
orswift-docc-render-artifact
DOCC_EXEC
DOCC_HTML_DIR
See the above mentioned pull request for new code that should be skipped in this case.