-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support nested groups on [GitLabTag] badge #7158
Conversation
|
t.create('Tag (project id latest by date)') | ||
.get('/29538796.json') | ||
.expectBadge({ label: 'tag', message: 'v2.0.0', color: 'blue' }) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks good. I reckon we should probably also add a test case with a repo that is nested in a group (and make that standard for gitlab badges).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds reasonable to me. I did add one such test as part of #7159 to update the Pipeline status badge and can use the same project as the test case here since they do have tags. However, that project doesn't have any releases published and I don't know of any nested examples that do for #7021.
I don't think trying to use such a target with a "no releases found" test would work either, since a bad project path route produces a 404 response as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Refs #7021 (comment)