[
https://issues.apache.org/jira/browse/SCM-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961984#comment-17961984
]
ASF GitHub Bot commented on SCM-541:
------------------------------------
jira-importer commented on issue #752:
URL: https://github.com/apache/maven-scm/issues/752#issuecomment-2964622303
**[Petr
Kozelka](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pkozelka)**
commented
Hello Kathryn,
I just tested your suggested option - see
https://github.com/pkozelka/git-demo/commit/8bc7b72317b3e5d80fa8fdfa3a692ddc211a8620
It shows that it causes git to **create an empty commit** , but that is not
a no-op and I believe it should not be used.
Instead, I think the output should be parsed for string "nothing to commit
(working directory clean)" when git fails and used for the no-op case.
> 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)
