NYCPlanning / NYCPlanning/data-engineering
Lint dbt projects from shared config
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
dbt-project-evaluator or similar, configured once rather than per project.
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 investigating how dbt projects are currently configured and where shared repository tooling could invoke dbt-project-evaluator or a similar linter. Done means dbt projects can be linted from one shared configuration without repeating setup in each project.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-engineering, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100