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 Gitea's organization-wide labels #6017

Closed
proton-ab opened this issue Apr 20, 2020 · 1 comment · Fixed by #6000
Closed

Support Gitea's organization-wide labels #6017

proton-ab opened this issue Apr 20, 2020 · 1 comment · Fixed by #6000

Comments

@proton-ab
Copy link
Contributor

What would you like Renovate to be able to do?
Assign requested label on PR upon creation

Describe the solution you'd like
Renovate should send additional request to Gitea in order to resolve IDs of organization labels

Describe alternatives you've considered
There is no alternative short of forcing end-user to not use this Gitea functionality, the end result is confusing to user as the config is valid but label is never applied.

Additional context
Gitea added support for organization-wide labels in go-gitea/gitea#10814. Such labels exist on all repositories that belong to organization and can be used like repository-native label. The only different is that second API call must be done in order to get ID<->Name mapping for such labels.

I have implemented support for organization labels in PR #6000, this issue is for tracking purposes only.

@renovate-release
Copy link
Collaborator

🎉 This issue has been resolved in version 19.216.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants