You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
fe60ca408b
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
|
8 years ago | |
|---|---|---|
| .. | ||
| admin | 8 years ago | |
| api/v1 | 8 years ago | |
| dev | 8 years ago | |
| org | 8 years ago | |
| repo | 8 years ago | |
| user | 8 years ago | |
| home.go | 8 years ago | |
| install.go | 8 years ago | |