Skip to content
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

Merged
merged 4 commits into from
Oct 16, 2021
Merged

Conversation

calebcartwright
Copy link
Member

@calebcartwright calebcartwright added the service-badge Accepted and actionable changes, features, and bugs label Oct 16, 2021
@shields-cd shields-cd temporarily deployed to shields-staging-pr-7158 October 16, 2021 15:45 Inactive
@calebcartwright calebcartwright temporarily deployed to shields-staging-pr-7158 October 16, 2021 15:59 Inactive
@shields-ci
Copy link

shields-ci commented Oct 16, 2021

Messages
📖 ✨ Thanks for your contribution to Shields, @calebcartwright!

Generated by 🚫 dangerJS against 90f25f6

@shields-cd shields-cd temporarily deployed to shields-staging-pr-7158 October 16, 2021 16:20 Inactive
t.create('Tag (project id latest by date)')
.get('/29538796.json')
.expectBadge({ label: 'tag', message: 'v2.0.0', color: 'blue' })

Copy link
Member

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).

Copy link
Member Author

@calebcartwright calebcartwright Oct 16, 2021

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

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@repo-ranger repo-ranger bot merged commit 694b07d into master Oct 16, 2021
@repo-ranger repo-ranger bot deleted the gitlab-tag-project branch October 16, 2021 18:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service-badge Accepted and actionable changes, features, and bugs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants