-
Notifications
You must be signed in to change notification settings - Fork 128
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
Provide disambiguated name in all/most cases #56
Labels
refactoring
Ruleset refactoring
Comments
Closed
We need to go further and introduce a strong policy of disallowing any packages to be left under ambiguous project names. Benefits:
The way to do it would be to convert |
AMDmi3
added a commit
that referenced
this issue
Aug 23, 2020
AMDmi3
added a commit
that referenced
this issue
Aug 25, 2020
AMDmi3
added a commit
that referenced
this issue
Sep 20, 2024
AMDmi3
added a commit
that referenced
this issue
Sep 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently it's common to set a disambiguated name for a less wide spread project, and leave wider spread project with a short name. It seems useful though to set disambiguated names in all cases.
The text was updated successfully, but these errors were encountered: