Community
Participate
Working Groups
GET on tags returns the list of tags where each tag has CommitLocation pointing at the tagged commit. The flat-layout repo page showing the list of tags also shows commit details next to each tag. So to display the list of 5 tags I have to make 6 xhr calls: 1 for tag and 5 for commits. It takes too much time and for longer lists it is way too long. I also noticed some inconsistency with our Git JSON representations: For instance: GET on commit returns commits and each commit has list of tag representations, while GET on tag returns tags and each tag has CommitLocation instead of commit representation. Another one is commits contain both Diffs and DiffLocation, which I guess should point at the same thing. Going to the point, what I need is to get commit details along with tags. The best would be to have some kind of param saying "Return commit representation instead of commit location". I will raise a separate bug for discussion how templates should look like for this. For now it would be enough to just return both Commit and CommitLocation for tag. Note that the same thing with branches and remote branches which are also displayed on the flat-repo page with commit details. This needs to be fixed too.
done use URL parameter commits=1 to get one commit per every tag
Ups... I missed "branch" in title. Than this bug is only half-done.
Same API for branches list and for remote details (applied to remote branches)