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

fix(platform/gerrit): URI encode branch in gerrit's getFile() #30753

Merged
merged 1 commit into from
Aug 14, 2024

Conversation

jwoe
Copy link
Contributor

@jwoe jwoe commented Aug 13, 2024

Changes

gerrit's client.ts now properly URI encodes the branch name, making it possible to for example use base branches containing slashes with gerrit.

Context

I was unable to use renovate with gerrit and a base branch containing a slash.

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

@jwoe jwoe changed the title URI encode branch in gerrit's getFile() fix(platform/gerrit): URI encode branch in gerrit's getFile() Aug 13, 2024
@rarkins rarkins enabled auto-merge August 14, 2024 07:17
@rarkins rarkins added this pull request to the merge queue Aug 14, 2024
Merged via the queue into renovatebot:main with commit d554483 Aug 14, 2024
38 checks passed
@renovate-release
Copy link
Collaborator

🎉 This issue has been resolved in version 38.27.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

zharinov pushed a commit to zharinov/renovate that referenced this pull request Aug 15, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 14, 2024
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 this pull request may close these issues.

3 participants