-
-
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
Supported nested groups on [GitLabPipeline] badge #7159
Conversation
|
|
||
async handle( | ||
{ project }, | ||
{ gitlab_url: baseUrl = 'https://gitlab.com', branch = 'master' } |
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.
GitLab now uses main
as the default branch name for new repos. In #5318 we made branch a required param but added a legacy redirect to /master
for existing users. Moving the route is an opportunity to update the default branch to main
(but keep the master redirect on the old route). i.e: /gitlab/pipeline/gitlab-org/gitlab
redirects to /gitlab/pipeline-status/gitlab-org/gitlab.svg?branch=master
but if you make the URL /gitlab/pipeline-status/gitlab-org/gitlab
from the frontend, that implies /gitlab/pipeline-status/gitlab-org/gitlab.svg?branch=main
. How does that sound?
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.
Yup, works for me
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.
Fixes #6427