[SCM-973] GitCheckInCommandNoBranchTest fails with Git 2.34.0+

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.12.0
• Fix Version/s: 1.12.1, 1.12.2, 2.0.0-M1
• Component/s: maven-scm-provider-gitexe
• Assignee: Michael Osipov
• Reporter: Michael Osipov
• Created: 27/Dec/21 21:22
• Updated: 28/Dec/21 20:14
• Resolved: 27/Dec/21 21:59

Description

Tests running on FreeBSD and Windows 10 gives me:

----------------------------------------------------------------------
Provider message
----------------------------------------------------------------------
The git-push command failed.
----------------------------------------------------------------------
----------------------------------------------------------------------
Command output
----------------------------------------------------------------------
remote: fatal: bad object refs/empty.txt
fatal: bad object refs/empty.txt
To file:///var/mosipov/Projekte/maven-scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/target/git_copy/
 ! [remote rejected] master -> master (missing necessary objects)
error: Fehler beim Versenden einiger Referenzen nach 'file:///var/mosipov/Projekte/maven-scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/target/git_copy/'

----------------------------------------------------------------------

The reason is in Git 2.34.0:

 * The ref iteration code used to optionally allow dangling refs to be
   shown, which has been tightened up.

Source: https://github.com/git/git/blob/2ae0a9cb8298185a94e5998086f380a355dd8907/Documentation/RelNotes/2.34.0.txt#L68-L69

We simply need to replace those broken refs with .gitkeep to retain dirs.

Issue Links

• links to: GitHub Pull Request #133