-
Notifications
You must be signed in to change notification settings - Fork 291
fix(controller): make git repo retain url suitable for use by external callers of URL() method #5350
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
base: main
Are you sure you want to change the base?
Conversation
…) method Signed-off-by: Kent Rancourt <[email protected]>
✅ Deploy Preview for docs-kargo-io ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #5350 +/- ##
==========================================
- Coverage 55.95% 55.93% -0.03%
==========================================
Files 407 407
Lines 29906 29939 +33
==========================================
+ Hits 16735 16745 +10
- Misses 12200 12222 +22
- Partials 971 972 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| internalURL string | ||
| externalURL string |
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.
I find the internalURL and externalURL naming quite confusing. Would something like url (or operationalURL) and canonicalURL maybe be better?
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.
Now that you've pointed it out, I agree the names aren't intuitive. You'd need to read the comments to understand. "Canonical" doesn't work because it's too similar to "normalized," and there's no real giant this is normalized. I'll noodle on this a bit. I agree there's a better naming scheme somewhere here that I've overlooked.
Fixes #5344
Internally, implementations of
git.Repohang on to URLs that often contain@username, but callers of theURL()method rightfully expect it to return the original URL that was provided to thegit.Clone()orgit.CloneBare()function.