Skip to content

Check out what I did! #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
3 commits merged into from
Feb 21, 2011
Merged

Check out what I did! #3

3 commits merged into from
Feb 21, 2011

Conversation

ags313
Copy link

@ags313 ags313 commented Feb 21, 2011

No description provided.

Andrzej Grzesik added 3 commits February 21, 2011 16:38
Added lookup for dotGitDirectory to check current dir, project/.git and parent/.git
TheSnoozer pushed a commit to TheSnoozer/git-commit-id-maven-plugin that referenced this pull request Jun 7, 2016
…tIdMojoDirtyFilesTest has been moved to GitCommitIdMojoIntegrationTest, since the determination of the dirty state should work regardless of native or the jgit implementation. Fix git-commit-id#2: The FileSystemMavenSandbox is intended to just be able to copy the git-Repository itself. As a result having the files besides the repository does no make sense. With that being said the repositories _git_with_no_changes and _git_with_changes needed to be refactored. Since the FileSystemMavenSandbox just copies the git-Repository itself all the repositories are dirty by default as long as they have files tracked. Hence the new _git_with_no_changes currently does no have files in it to be able to represent a repository with no changes. Fix git-commit-id#3 (git-commit-id#236): The ProcessBuilder inside NativeGitProvider always told the user that the 'git status -s' command was not issued correctly and printed the usage manual of the command itself. Since the 'git status -s' command just checks if there was a return value from the command the NativeGitProvider always assumed that the repository was in a dirty state....
This pull request was closed.
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.

1 participant