Skip to content

Conversation

@alexrichey
Copy link
Contributor

@alexrichey alexrichey commented Dec 15, 2025

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

@codecov
Copy link

codecov bot commented Dec 15, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.75%. Comparing base (f7a753c) to head (d8e59aa).

Additional details and impacted files

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@alexrichey alexrichey marked this pull request as ready for review December 15, 2025 16:54
@fvankrieken
Copy link
Contributor

Sounds good to me! We should certainly be thoughtful about how we organize these but seems like a nice way to do exactly what you're doing. I have a bunch of saved sql queries that should probably live somewhere like this

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(not a strong feeling) maybe something like operations is better than admin? admin always makes me think of like elevated/root access to change the environment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants