[
https://issues.apache.org/jira/browse/SCM-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962588#comment-17962588
]
ASF GitHub Bot commented on SCM-694:
------------------------------------
jira-importer opened a new issue, #902:
URL: https://github.com/apache/maven-scm/issues/902
**[Olivier
Lamy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=olamy)**
opened
**[SCM-694](https://issues.apache.org/jira/browse/SCM-694?redirect=false)** and
commented
rename a file then you get
```
1. On branch master
1. Changes to be committed:
1. (use "git reset HEAD <file>..." to unstage)
#
1. renamed: foo/bar/wine.xml -> foo/newbar/wine.xml
#
```
Before executing git commit, the commit check status.
But failed as renamed is not parsed. So nothing to commit.
---
**Affects:** 1.8
> git checkin command doesn't work with renamed files
> ---------------------------------------------------
>
> Key: SCM-694
> URL: https://issues.apache.org/jira/browse/SCM-694
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: New Feature
> Components: maven-scm-provider-gitexe
> Affects Versions: 1.8
> Reporter: Olivier Lamy
> Assignee: Olivier Lamy
> Priority: Major
> Fix For: 1.8.1
>
>
> rename a file then you get
> {code}
> # On branch master
> # Changes to be committed:
> # (use "git reset HEAD <file>..." to unstage)
> #
> # renamed: foo/bar/wine.xml -> foo/newbar/wine.xml
> #
> {code}
> Before executing git commit, the commit check status.
> But failed as renamed is not parsed. So nothing to commit.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
