Take preferece of tags over branches when selecting the stable version #3331
I changed a couple of things here.
Let me know if you dislike this from this PR and I will remove them.
The interesting commit with the new logic to take a look is fd0b406
I will add more tests for this new logic.
The text was updated successfully, but these errors were encountered:
This allows us to have the same `verbose_name` for different type of versions (for example, '2.0' could both a tag and a branch). If this happen, we want to keep them both. In the UI, it will say just `"2.0"` for the branch and `"2.0 (c0d25453)"` for the tag. This could be improved later if necessary.
Now, this logic is like this: - if the project has any Version that is a TAG, the highest version will only be a TAG also (BRANCH are not considered) - if the project doesn't have any TAG the highest version will be a BRANCH (or UNKNOWN in the worst case)