-
Notifications
You must be signed in to change notification settings - Fork 15
Align ecosystem / package colors with GitHub Linguist #2603
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
Comments
These colors seem to be defined for languages, not package managers, so I assume a map between those two would also need to be done. |
More generally, the colors are defined per file extensions, no matter whether they belong to a language or package manager. For example, Linguist does define a color for Gradle files. |
For further tuning of the ecosystem colors used in the server UI (see for example #2603), show the current colors in the admin/colors page. Signed-off-by: Jyrki Keisala <jyrki.keisala@doubleopen.org>
For further tuning of the ecosystem colors used in the server UI (see for example #2603), show the current colors in the admin/colors page. Signed-off-by: Jyrki Keisala <jyrki.keisala@doubleopen.org>
To make developers feel more at home, we should consider aligning our ecosystem / package colors to those defined by GitHub Linguist.
However, note that there still would be a difference as to how GitHub and ORT Server display the colors for a given Git repository: While GitHub looks at the file extensions of all contained files, ORT (Server) looks at the file extensions of the definition files only. That is, a Kotlin project managed by Gradle would be (mostly) a Kotlin "thing" for GitHub, but a Gradle "thing" for ORT (Server).
The text was updated successfully, but these errors were encountered: