warn about old base revisions
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 67
- Forks
- 52
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 54
Description
If a patch is submitted based on an old base revisions,, it inherits its issue and can be affected by new ones which depend on time, e.g. outdated certificates, test suites, documents (e.g. perfdocs).
4 weeks (1 development cycle) could be a threshold but the certificates which will be expiring are updated in the 3 weeks up to that date, hence 1 week might be better as threshold.
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
No files, tests, or entry points are named. Start by locating where submitted patches expose their base revisions, then clarify the warning threshold and affected checks; done means an old-base patch is detected and the chosen warning behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100