[
https://issues.apache.org/jira/browse/SCM-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961983#comment-17961983
]
ASF GitHub Bot commented on SCM-541:
------------------------------------
jira-importer opened a new issue, #752:
URL: https://github.com/apache/maven-scm/issues/752
**[Kathryn
Huxtable](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=khuxtable)**
opened
**[SCM-541](https://issues.apache.org/jira/browse/SCM-541?redirect=false)** and
commented
Without it, git returns a status of 1 when there is nothing to commit. This
makes the wagon-scm and other processes that depend on this being a no-op fail.
I think that git should not fail on an empty commit, and adding the
--allow-empty option on commits would achieve that.
---
No further details from
[SCM-541](https://issues.apache.org/jira/browse/SCM-541?redirect=false)
> GitExe commit should include --allow-empty option
> -------------------------------------------------
>
> Key: SCM-541
> URL: https://issues.apache.org/jira/browse/SCM-541
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-gitexe
> Reporter: Kathryn Huxtable
> Priority: Minor
>
> Without it, git returns a status of 1 when there is nothing to commit. This
> makes the wagon-scm and other processes that depend on this being a no-op
> fail.
> I think that git should not fail on an empty commit, and adding the
> --allow-empty option on commits would achieve that.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
