-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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(git-url): clean up state of parsed URL #24306
Conversation
This ensures the state of `parsedUrl` doesn't have authentication credentials prior to appending the authentication tokens.
We were missing the path in the URL to ensure the test behaves as expected. Co-authored-by: Tobias <github@tobiasgabriel.de>
The library doesn't allow us to update `password`, which is covered by `token` anyway. Co-authored-by: Tobias <github@tobiasgabriel.de>
@Shegox it should be good now :) |
@Shegox do you know if the broken tests are related to real expectations? |
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.
needs prettier fix
Looking at the patch, it doesn't seem strictly related - more like side effects of the status quo. @Shegox should we move forward with this? If so, I'll fix the test expectations and address the coding style issues. |
Signed-off-by: Luís Cobucci <lcobucci@gmail.com>
Signed-off-by: Luís Cobucci <lcobucci@gmail.com>
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.
🎉 This PR is included in version 36.93.7 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
@@ -77,6 +77,14 @@ describe('util/git/url', () => { | |||
'https://x-access-token:token@github.com/some/repo' |
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.
Wyd
Changes
This ensures the state of
parsedUrl
doesn't have authentication credentials prior to appending the authentication tokens.Context
This is meant to verify and solve the issue described here.
Documentation
How I've tested my work
I have verified these changes via: