mozilla / mozilla/probe-scraper
Allow ignoring commits before a set date in `repositories.yaml`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 73
- Avg merge
- 10h
- Merged PRs (30d)
- 3
Description
Sometimes, when adding Glean to new products, there's a transition phase in which the registry files are wrong or broken. The probe-scraper has a way to deal with that by specifying which commit date to start considering commits from.
Given how often we hit this problem with the application, it might be useful to have this as an option in repositories.yaml.
Contributor guide
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 repositories.yaml configuration and compare the existing date-handling approach in probe_scraper/scrapers/git_scraper.py at lines 14-32. Trace how repository settings reach commit scraping, then verify that a configured date causes earlier commits to be ignored while existing behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100