Protect against rewriting pushed commits
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 341
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
For 95% of cases, checking that a commit is not part of origin/<branch> (or maybe any <remote>/<branch>) is a good idea. Worth adding a flag to opt out of the protection, of course.
(Very tempting to also add a special specifier for unpushed commits for faster rewriting, but that's probably on the too lazy/too ambiguous side.)
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 tracing how git-backdate selects commits and resolves origin/ or other remote refs. Clarify whether protection covers all remotes and how the opt-out flag should behave. Done means pushed commits are protected by default, with an explicit way to bypass that protection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100