NYCPlanning / NYCPlanning/data-engineering
db-pluto 26v2 QA Draft 3-newer-pts
Open
Nobody has claimed this yet.
db-pluto
QA
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
This issue was created as a part of this action.
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 with the linked GitHub Actions run and inspect the draft build zip in DigitalOcean. The issue does not identify a failing test, file, expected result, or requested change, so first determine what QA discrepancy needs investigation. Done should be a clearly documented QA result and an identified follow-up change if the build is incorrect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100