-
Notifications
You must be signed in to change notification settings - Fork 3
build CEQR schools 2026 #2132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
build CEQR schools 2026 #2132
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files
☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
d042a36 to
a8b99da
Compare
a8b99da to
f6a2509
Compare
f6a2509 to
5b05058
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so I don't have to run a dev container to run builds that use geosupport, modeled on the in-use ceqr_dep_monthly.yml action. couldn't test this with workflow_dispatch untill it's merged
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pretty sure the LCGMS we get form CAPS for CEQR schools is different that what we get from the DOE website and use in the doe_lcgms ingest template. need to use library to archive this to the recipe postgres DB anyway so it wasn't worth resolving to a single ingest template to build the CEQR schools datasets
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we give this a different id then? Feels unlikely that it would happen by accident, but we still shouldn't have two different ingest/library templates with the same dataset id.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bumping this comment - other than that, good to go
related to #2082
hopefully we modernize how we handle these datasets before we need to build them next year (definitely said the same thing last year)