[SCM-852] maven-scm-plugin:check-local-modification should optionally check for unpushed commits
- Dominant language
- Java
- Stars
- 104
- Forks
- 189
- Avg merge
- 17h 46m
- Merged PRs (30d)
- 6
Description
**[Konrad Windszus](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kwin)** opened **[SCM-852](https://issues.apache.org/jira/browse/SCM-852?redirect=false)** and commented
Currently the goal `check-local-modification` only checks for local changes. But with distributed SCM systems it is very often also desirable to enforce that all local commits have been pushed to the origin as well. It would be good to optionally check for unpushed commits or not yet fetched commits with that goal.
---
**Affects:** 1.9.5
**Issue Links:**
- [SCM-970](https://issues.apache.org/jira/browse/SCM-970) Have separate APIs for distributed and centralized version control
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the maven-scm-plugin goal check-local-modification and read the linked SCM-970 discussion about separate distributed and centralized version-control APIs. Define how an optional check should cover unpushed or not-yet-fetched commits across supported distributed SCM systems, then verify the goal's existing behavior and add coverage for the selected option.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100