-
Notifications
You must be signed in to change notification settings - Fork 653
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
introduce in memory git metadata 2 #1244
introduce in memory git metadata 2 #1244
Commits on Jun 24, 2017
-
Start decoupling the runtime of gitversion from libgit2
This hopefully will end up with us getting rid of normalisation and making GitVersion much faster
Configuration menu - View commit details
-
Copy full SHA for 271a403 - Browse repository at this point
Copy the full SHA 271a403View commit details -
This reduces scanning the branch commits by one pass
Configuration menu - View commit details
-
Copy full SHA for e44aa1b - Browse repository at this point
Copy the full SHA e44aa1bView commit details -
Fixed ReleaseBranchScenarios tests which needed TrackReleaseBranchesV…
…ersionStrategy to be fixed after changes to TaggedCommitVersionStrategy
Configuration menu - View commit details
-
Copy full SHA for 1677a83 - Browse repository at this point
Copy the full SHA 1677a83View commit details -
Configuration menu - View commit details
-
Copy full SHA for 20f7a14 - Browse repository at this point
Copy the full SHA 20f7a14View commit details
Commits on Jun 25, 2017
-
More abstraction and calculating things early
Commit counting needs to be revisited, but overall promising
Configuration menu - View commit details
-
Copy full SHA for b5b3962 - Browse repository at this point
Copy the full SHA b5b3962View commit details
Commits on Jul 2, 2017
-
Configuration menu - View commit details
-
Copy full SHA for 81ef971 - Browse repository at this point
Copy the full SHA 81ef971View commit details -
Commit counting behavior has changed when using config files, the com…
…mit count comes from the commit the config was updated These tests can safely change
Configuration menu - View commit details
-
Copy full SHA for cdcb3e4 - Browse repository at this point
Copy the full SHA cdcb3e4View commit details -
This test can have it's commit count updated
It is checking the merge doesn't reset the commit count, the new commit counting logic slightly changes the source commit which means it is the merge base rather than the first commit on the merged branch, looks ok to update this
Configuration menu - View commit details
-
Copy full SHA for d2fa443 - Browse repository at this point
Copy the full SHA d2fa443View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9bdce74 - Browse repository at this point
Copy the full SHA 9bdce74View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2f22169 - Browse repository at this point
Copy the full SHA 2f22169View commit details
Commits on Dec 5, 2017
-
Configuration menu - View commit details
-
Copy full SHA for 3cbf66a - Browse repository at this point
Copy the full SHA 3cbf66aView commit details -
Merge remote-tracking branch 'upstream/master' into feature/Introduce…
…InMemoryGitMetadata2
Configuration menu - View commit details
-
Copy full SHA for f92eef4 - Browse repository at this point
Copy the full SHA f92eef4View commit details -
Configuration menu - View commit details
-
Copy full SHA for c0167f5 - Browse repository at this point
Copy the full SHA c0167f5View commit details