Skip to content
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

Commits on Jun 24, 2017

  1. Start decoupling the runtime of gitversion from libgit2

    This hopefully will end up with us getting rid of normalisation and making GitVersion much faster
    JakeGinnivan committed Jun 24, 2017
    Configuration menu
    Copy the full SHA
    271a403 View commit details
    Browse the repository at this point in the history
  2. Added tags to git metadata

    This reduces scanning the branch commits by one pass
    JakeGinnivan committed Jun 24, 2017
    Configuration menu
    Copy the full SHA
    e44aa1b View commit details
    Browse the repository at this point in the history
  3. Fixed ReleaseBranchScenarios tests which needed TrackReleaseBranchesV…

    …ersionStrategy to be fixed after changes to TaggedCommitVersionStrategy
    JakeGinnivan committed Jun 24, 2017
    Configuration menu
    Copy the full SHA
    1677a83 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    20f7a14 View commit details
    Browse the repository at this point in the history

Commits on Jun 25, 2017

  1. More abstraction and calculating things early

    Commit counting needs to be revisited, but overall promising
    JakeGinnivan committed Jun 25, 2017
    Configuration menu
    Copy the full SHA
    b5b3962 View commit details
    Browse the repository at this point in the history

Commits on Jul 2, 2017

  1. Configuration menu
    Copy the full SHA
    81ef971 View commit details
    Browse the repository at this point in the history
  2. 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
    JakeGinnivan committed Jul 2, 2017
    Configuration menu
    Copy the full SHA
    cdcb3e4 View commit details
    Browse the repository at this point in the history
  3. 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
    JakeGinnivan committed Jul 2, 2017
    Configuration menu
    Copy the full SHA
    d2fa443 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    9bdce74 View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    2f22169 View commit details
    Browse the repository at this point in the history

Commits on Dec 5, 2017

  1. Configuration menu
    Copy the full SHA
    3cbf66a View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    f92eef4 View commit details
    Browse the repository at this point in the history
  3. Fixed build issues

    JakeGinnivan committed Dec 5, 2017
    Configuration menu
    Copy the full SHA
    c0167f5 View commit details
    Browse the repository at this point in the history