The current CI implementation makes it hard to discuss small changes to a bigger PR
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10
- Forks
- 40
- Avg merge
- 21h 24m
- Merged PRs (30d)
- 8
Description
Migrated from https://pulp.plan.io/issues/5456
In the travisscripts, the commit messages of a pr are checked to conform to a specific format. If they do not conform, the scripts fail very early skipping all 'real' tests.
This makes it impossible to add incremental changes in individual commits (later to be squashed) to an existing PR while stilll get reports for failing tests.
If commit message validation was extracted as a separate test, one could use for example the git commit --fixup aabbccdd feature of git, while the validator would still block the merge button.
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 locating the travisscripts commit-message validation and the CI flow that runs the real tests. Separate validation from the test execution so nonconforming commits no longer prevent test reports, while the validator still blocks merging. Done means incremental fixup commits can receive test results and merge gating still enforces the format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- ci-cd, tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100