[
https://issues.apache.org/jira/browse/SCM-852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963382#comment-17963382
]
ASF GitHub Bot commented on SCM-852:
------------------------------------
jira-importer opened a new issue, #1077:
URL: https://github.com/apache/maven-scm/issues/1077
**[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
> maven-scm-plugin:check-local-modification should optionally check for
> unpushed commits
> --------------------------------------------------------------------------------------
>
> Key: SCM-852
> URL: https://issues.apache.org/jira/browse/SCM-852
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-plugin
> Affects Versions: 1.9.5
> Reporter: Konrad Windszus
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
