-
Notifications
You must be signed in to change notification settings - Fork 28
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
Add back go-source tag #127
Comments
Can I do this again haha @abhinav |
Sure, @SoulPancake, go for it! |
@SoulPancake if you're at it, it would be great if you could take this PR into account (#128) and added some field that lets users override the source value via the config. If not, I can always make another PR if that'd be welcomed. |
It seems to me that if we want to support alternative VCSs per #128, we can't hard-code it to GitHub's directory/file path scheme like we did previously. We'll need something like a |
Yeah, I think so. I would add both variables you mentioned. Only if both are set, add By default, I wouldn't set |
pkg.go.dev uses the go-source for VCS hosts that it doesn't recognize.
We should add back go-source.
Thanks to @hacdias for reporting:
Originally posted by @hacdias in #83 (comment)
The text was updated successfully, but these errors were encountered: