1. 28 Jul, 2016 1 commit
  2. 27 Jul, 2016 1 commit
    • 마누엘's avatar
      routers/repo/release: Use correct branch reference (#3330) · fe60ca40
      마누엘 authored
      When calculating the current behind commit count the calculation should
      use the current release target to get the total commit count. Should the
      release target not exist anymore the calculation will return zero for
      the newest release on that target. Older releases on that target will then
      use that calculated commit count as reference.
      
      The only use case that is now somehow invalid is when the release target
      was merged / deleted after a tag on that release target:
      
          master 1 - - - - - - - 6
                  \             /
          branch   2 - 3 - 4 - 5
      
      When `4` is the last tag on branch `branch` and the branch `branch` is not
      yet deleted the calculated numbers would be:
      
          1 commits to branch since this release
      
      Now if the branch `branch` gets deleted the calculation function will not
      find the branch and use the commit count of the newest release (`4`) as
      reference resulting in:
      
          0 commit to branch since this release
      
      This fixes #3326
      fe60ca40
  3. 26 Jul, 2016 5 commits
  4. 25 Jul, 2016 3 commits
  5. 24 Jul, 2016 2 commits
  6. 23 Jul, 2016 17 commits
  7. 22 Jul, 2016 3 commits
  8. 21 Jul, 2016 5 commits
  9. 17 Jul, 2016 3 commits