Jwilber/load nb from subpackages #128
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jwilber
requested review from
jomitchellnv,
jstjohn,
malcolmgreaves,
skothenhill-nv and
pstjohn
as code owners
malcolmgreaves
approved these changes
Aug 30, 2024
pstjohn
reviewed
Aug 30, 2024
jstjohn
approved these changes
Aug 31, 2024
jwilber
force-pushed
the
jwilber/load-nb-from-subpackages
branch
from
f92bb26 to
f1d4947
Compare
|
/build-ci |
pstjohn
added a commit
that referenced
this pull request
Sep 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This automates/outlines the pulling of
sub-package-specific content.What we pull/how we structure the sub-packages is subject to change, but this outlines pulling:
Developer guidetab.Examplestab.I expect be adding/editing automation utilities in some capacity, so I refactored the script into file-specific utility funcs, so it's easier to follow.
Below is what gets generated (again, subject to change on how this looks eventually):
Developer guide
READMEs are loaded as the main documentation entry point, for each sub-package (the tab name is the README's first header).Examples:
Notebooks for each sub-package. This assumes that each sub-package stores them in a dir,
examples/.