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
Hi, I'm having trouble with a GitLab v13.x instance and the release API call: https://example.com/api/v4/projects/<owner>%2F<project>/releases/<sometag>
Any tag that does not exist is responded to with a 403 Forbidden, only tags that exist would work.
This ruins the use of IsScmNotFound.
Would a change make sense that considers "Forbidden" errors as not found?
The text was updated successfully, but these errors were encountered:
manuelstein
added a commit
to manuelstein/jx-changelog
that referenced
this issue
Oct 5, 2021
private gitlab returns forbidden on non-existing tags
see also [my issue on go-scm] regarding response codes(jenkins-x/go-scm#302)
go-scm helper IsScmNotFound() cannot distinguish the gitKind, so aplied the fix in isReleaseNotFound()
Signed-off-by: Manuel Stein <[email protected]>
Hi, I'm having trouble with a GitLab v13.x instance and the release API call:
https://example.com/api/v4/projects/<owner>%2F<project>/releases/<sometag>
Any tag that does not exist is responded to with a 403 Forbidden, only tags that exist would work.
This ruins the use of IsScmNotFound.
Would a change make sense that considers "Forbidden" errors as not found?
The text was updated successfully, but these errors were encountered: