Quantco / Quantco/quant-ranger
Crater-like testing to gauge downstream effects
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 0
- Avg merge
- 3h 39m
- Merged PRs (30d)
- 6
Description
Hey,
crater is used by the Rust team for running compiler/cargo/tooling changes through a small-to-very-large number of crates to judge the effects on the downstream ecosystem.
A similar feature in quant-ranger might be helpful for larger refactors on repositories. If such a time comes up, this issue might be nice for documentation/awareness.
Enjoy your day 🐞
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 reading the linked Crater project and comparing its downstream-testing model with quant-ranger's current maintenance workflow. The issue names no files, tests, entry points, or acceptance criteria, so define the intended scope and what a completed repository-wide impact assessment should demonstrate before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100