[jira] [Assigned] (YETUS-983) test-patch confused by multiple commits that include rename

["Nick Dimiduk (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YETUS-983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Dimiduk reassigned YETUS-983:
----------------------------------

    Assignee: Nick Dimiduk

> test-patch confused by multiple commits that include rename
> -----------------------------------------------------------
>
>                 Key: YETUS-983
>                 URL: https://issues.apache.org/jira/browse/YETUS-983
>             Project: Yetus
>          Issue Type: Bug
>            Reporter: Allen Wittenauer
>            Assignee: Nick Dimiduk
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> A long-standing bug has been that precommit is confused by a patch with multiple commits. Based upon some observations in a few private repositories, there appears to be some correlation between:
> * a commit that renames a file
> * a commit that changes the content of the file post-rename
> and git format-patch --dry-run.   Because it is in dry-run mode, the rename doesn't take place, so the next commit in the sequence to the renamed file fails.
> Squashing the commits is the obvious workaround.  Fixing this will likely require much more in-depth analysis of the patchfile and determining if dry-run should be skipped.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)