Skip to content

Conversation

TheSnoozer
Copy link
Collaborator

@ktoso ,
Well I think this tiny bit of code-change already fixes #146.
In case of detached HEAD-State the JGit-Implementation uses the SHA of the commit. With this PR the same behavoir is implemented for the Native Git-Implementation.

Considered following:

  1. Even if the the general Execution-Error (git-Binary couldn't be found), this error will be triggered by the "getCommitId"-Call.
  2. In Terms of Performance we could swap "determineBranchName" and "getCommitId" in the GitDataProvider. When the "getCommitId" will be triggered before the "determineBranchName" we could save the SHA of the current commit inside the Native-Git-Implementation instead of just asking again.

Additional comments are welcome...

… in detached HEAD-State and not in a CI-Environment, thats the same behavoir as in JGit-Implementation
@ktoso
Copy link
Collaborator

ktoso commented Dec 12, 2014

Nice one! I think this is a nice fix for the time being!

ktoso added a commit that referenced this pull request Dec 12, 2014
@ktoso ktoso merged commit b0bf006 into git-commit-id:master Dec 12, 2014
@TheSnoozer
Copy link
Collaborator Author

Thanks :)

@ktoso ktoso added this to the 2.1.13 milestone Mar 10, 2015
@TheSnoozer TheSnoozer modified the milestones: 2.1.12, 2.1.13 Apr 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

FAILED: runGitDescribeWithMatchOption, has trouble on Travis
2 participants