Update the CLI docs to use the developer-tooling repository as a submodule #1211
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The goal is to make everyone's lives easier by firstly changing the docs to use a submodule, and secondly, create a pull-request keeping it in sync whenever the CLI gets released. You can see an example of a PR that would be created in such events here: #1210
The automation work can be followed in this PR:
Note: initially the goal was to use symlinks to the submodule but instead hardcopies need to be made because of a bug in docusaurus .
Regardless, your workflow shouldn't change as the submodules get fetched after running
yarn
oryarn install
.