Third-party stubtest: Dashboard
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.1k
- Forks
- 2.1k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 82
Description
Provisional idea:
Currently, some third-party packages with frequent releases are annoying. If we use a version range (e.g. 1.2.* or ~= 1.2.3), stubtest breaks even on minor, non-user facing changes, and will create daily tickets unless fixed. When using a fixed version (e.g. 1.2.3), it will frequently create tickets by stubsabot to update the version.
I think it would be nice to have a dashboard instead (updated daily) that just lists the packages that need updates, either because stubsabot detected a change, or because stubtest broke.
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 by reviewing the existing stubtest and stubsabot processes mentioned in the issue to understand how package changes and stubtest failures are detected. Done would be a daily-updated dashboard listing packages needing updates for either reason, but the issue does not specify implementation entry points or tests.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100