1. 08 Aug, 2016 1 commit
  2. 06 Aug, 2016 1 commit
  3. 05 Aug, 2016 6 commits
  4. 04 Aug, 2016 11 commits
  5. 03 Aug, 2016 1 commit
  6. 02 Aug, 2016 1 commit
  7. 24 Jul, 2016 13 commits
  8. 23 Jul, 2016 3 commits
  9. 15 Jul, 2016 1 commit
    • remote: Handle missing config values when deleting a remote · d81cb2e4
      Somehow I ended up with the following in my ~/.gitconfig:
      [branch "master"]
      remote = origin
      merge = master
      rebase = true
      
      I assume something went crazy while I was running the git.git tests
      some time ago, and that I never noticed until now.
      
      This is not a good configuration, but it shouldn't cause problems. But
      it does. Specifically, if you have this in your config, and you
      perform the following set of actions:
      
      create a remote
      fetch from that remote
      create a branch off of the remote master branch called "master"
      delete the branch
      delete the remote
      
      The remote delete fails with the message "Could not find key
      'branch.master.rebase' to delete". This is because it's iterating over
      the config entries (including the ones in the global config) and
      believes that there is a master branch which must therefore have these
      config keys.
      
      https://github.com/libgit2/libgit2/issues/3856
      David Turner committed
  10. 06 Jul, 2016 1 commit
  11. 05 Jul, 2016 1 commit