NYCPlanning / NYCPlanning/data-engineering
CEQR Hub build frequency
Open
Nobody has claimed this yet.
db-ceqr
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
We should probably build CEQR Data Hub monthly. It depends on PLUTO minor releases so it's similar to GFT.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining how the GFT build is configured, then trace the CEQR Data Hub build and its dependency on PLUTO minor releases. Define the monthly scheduling behavior and confirm that a scheduled build is triggered at the intended cadence; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100