1. 27 May, 2014 2 commits
  2. 23 May, 2014 1 commit
  3. 15 May, 2014 1 commit
  4. 17 Apr, 2014 1 commit
  5. 08 Apr, 2014 1 commit
  6. 03 Apr, 2014 3 commits
  7. 02 Apr, 2014 1 commit
  8. 28 Mar, 2014 1 commit
  9. 19 Mar, 2014 2 commits
  10. 18 Mar, 2014 1 commit
  11. 13 Mar, 2014 1 commit
  12. 12 Mar, 2014 3 commits
  13. 10 Mar, 2014 4 commits
  14. 27 Feb, 2014 1 commit
  15. 10 Feb, 2014 1 commit
  16. 07 Feb, 2014 1 commit
    • Make sure requested version tag gets downloaded · 4593e3c3
      There is a subtle bug in how the git module currently works. If the
      version you request is a tag name, and you've already got the repo
      cloned, and the tag name is a new tag, but refers to the already checked
      out working copy, the git module would exit early without change. This
      is bad as it means the new tag ref was not fetched and could not be used
      in later tasks.
      
      This change will check if the version is a remote tag, and if the tag
      doesn't exist locally. If that is true, it'll do a fetch.
      
      The activity could still be seen as not a change, because the working
      copy won't be updated, if the new tag refers to the already checked out
      copy, but that's not different than before and can be fixed as a more
      comprehensive overhaul of tracking change in the git module.
      Jesse Keating committed
  17. 31 Jan, 2014 1 commit
  18. 28 Jan, 2014 1 commit
  19. 23 Jan, 2014 3 commits
  20. 15 Jan, 2014 1 commit
  21. 11 Jan, 2014 2 commits
  22. 13 Dec, 2013 1 commit
  23. 03 Dec, 2013 1 commit
  24. 02 Dec, 2013 2 commits
  25. 25 Nov, 2013 2 commits
  26. 18 Nov, 2013 1 commit