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.
Talking to @damonmcc about this, and I'd love to have the my QA for dataset modifications result in something a little less throwaway - ie instead of slopping some queries into DBeaver, it'd be nice to make a durable, reusable little notebook instead.
The main reason for centralizing them in one top-level folder is that a little further down the road we can have a marimo notebook server in the
apps/folder, which we can bundle up with dcpy in Docker, and deploy to Azure as a companion to the QA/AC app. It'd be nice to have a single folder to point at, as opposed to having notebooks scattered around the repo (e.g. in products/pluto/my_notebook.py).I mostly want input before I add my notebook for PLUTO