-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Delete some of our logos (part 1); affects [endpoint] #2857
Conversation
Gah - I'd forgotten that there are some tests and services which directly reference logos - thanks, Continuous Integration! I'll come back to this and get all the tests passing tomorrow. The visuals shouldn't change though. |
Nice work on this, looking really good 👍 |
Nice! The tables really are so much work, it's cool this is moving ahead. Re two of these:
|
mostly non-controversial ;) |
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.
This LGTM!
# Conflicts: # core/base-service/base.spec.js
9b3deb6
Refs #2510
I'm going to delete or change some more logos in a further PR or two, but lets start off with the (hopefully) non-controversial ones. I think in all of these cases it is fairly clear-cut that we are not losing anything by removing our icon in favour of simple-icons now that we apply a sensible colour by default.
*
*
Note this one is out-of-date now, but there's a PR open to update to the new slack logo: simple-icons/simple-icons#1172 This is one of the other nice things about not maintaining our own logos.There are a few more to go, but I'll be quite glad when I don't need to make any more of these tables! :)