-
Type:
Bug
-
Resolution: Low Engagement
-
Priority:
Low
-
None
-
Affects Version/s: 4.12.0, 4.14.0, 5.1.0
-
Component/s: API - REST, Repository - Branches / Tags
-
10
-
Severity 3 - Minor
-
3
A customers' REST request to
/rest/api/latest/projects/IESD/repos/iesd-17.1/branches
with the filter -SEC-17-.1/FOD, returned
{"id":"refs/heads/SEC-17.1/FOD","displayId":"SEC-17.1/FOD","type":"BRANCH","latestCommit":"b9edef077dbc93bb2a8d46e58b0545f0fc513c45","latestChangeset":"b9edef077dbc93bb2a8d46e58b0545f0fc513c45","isDefault":false},
{"id":"refs/heads/SEC-17.1/FOD","displayId":"SEC-17.1/FOD","type":"BRANCH","latestCommit":"97953adac57f8fea837e88fa797ef617234fe7c1","latestChangeset":"97953adac57f8fea837e88fa797ef617234fe7c1","isDefault":false}]
But when performing
git for-each-ref --sort=-committerdate --format="%(refname)%02%(objectname)" refs/heads/
there was only a single entry for the branch.