You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@xanarin pointed out that Git allows a tag and a branch to have the same name. So the fix in #16 introduces a potential ambiguity, by no longer allowing tags/v1.2.3.
If you push a branch that has the same name as an existing tag, then GitLab will run a pipeline for the correct commit, but incorrectly thinks the pipeline is for "a tag" (the tag attribute on the returned pipeline object is true).
Even more confusing, scope='tags' returns an incorrect list in this case.
@xanarin pointed out that Git allows a tag and a branch to have the same name. So the fix in #16 introduces a potential ambiguity, by no longer allowing
tags/v1.2.3
.The problem is that the GitLab list project pipelines API just says
ref
, and I've proven that you cannot passtags/foo
:The API does however provide
scope
:scope
So perhaps we could look at the ref to see if
tags/
is present, and if so, strip it, and then passscope=tags
.The text was updated successfully, but these errors were encountered: