-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
It's confusing when to use go_modules
vs gomod
#6577
Comments
This is not just true for Go, but also for a number of other ecosystems. The example below from one of this repo's workflows shows the following items differ:
dependabot-core/.github/workflows/images-latest.yml Lines 36 to 52 in 82906a9
Should this issue cover all of these? |
@markdorison This was especially confusing when wanting to maintain the ecosystem-label when there is only one ecosystem then dependabot only adds the "dependency" label, but for easier search I'd like to have the ecosystem-label everywhere. It was a bit hard to find which label is actually added. Via this issue I know that I should add the label "github_actions" instead of the ecosystem name "github-actions". |
Is there an existing issue for this?
Code improvement description
gomod
is a leftover from whengo
didn't have a cannonical package manager, so there was thego dep
project and several others.We've also now got
go_modules
and it's confusing which to use where... for example:We should standardize on a cannonical name for go modules. We could use
go
, since I doubt there will be another package manager in that ecosystem, but that also feels risky in case I'm wrong... sogo_modules
is probably the safest solution.So this is a reminder to me to investigate what it'd take to standardize on that.
The text was updated successfully, but these errors were encountered: