21–30 of 60 posts
SSO is important for enterprise.. but github presents a challenge where devs usually have pre-existing personal accounts which are added to company github accounts, rather than the company account being used.
Tangentially related, but on our slack this morning everyone is griping about the updated blue text color on repo pages at Github. It's pretty ugly.
Not only that but why would you change the clean top bar? The dark one that is live for weeks now is worse than the old one.
Tangentially related, but on our slack this morning everyone is griping about the updated blue text color on repo pages at Github. It's pretty ugly.
I too thought I was going crazy when I noticed it this morning... Funny, but that shade (or one very much like it) is forever etched into my brain as "porn blue" thanks to a k10k issue back in the day when the internet was still referred to as the information super highway and nobody knew what we were doing. Here's an excerpt from the first "lesson": You must never use this colour. You can like it as much as you want…
Earlier quoted context omitted.
This is for colourblind people.
Still doesn't make it look good. If thats an issue they could always have an optional setting to enable colorblind mode.
And if colorblind people aren't inconvenienced (and don't have to navigate to a menu to de-inconvenience themself) then that's enough of a reason for me.
Tangentially related, but on our slack this morning everyone is griping about the updated blue text color on repo pages at Github. It's pretty ugly.
Tangentially related, but on our slack this morning everyone is griping about the updated blue text color on repo pages at Github. It's pretty ugly.
I too thought I was going crazy when I noticed it this morning... Funny, but that shade (or one very much like it) is forever etched into my brain as "porn blue" thanks to a k10k issue back in the day when the internet was still referred to as the information super highway and nobody knew what we were doing. Here's an excerpt from the first "lesson": You must never use this colour. You can like it as much as you want…
Tangentially related, but on our slack this morning everyone is griping about the updated blue text color on repo pages at Github. It's pretty ugly.
Tangentially related, but on our slack this morning everyone is griping about the updated blue text color on repo pages at Github. It's pretty ugly.
github.css: https://www.diffchecker.com/STyCXVyk framework.css: https://www.diffchecker.com/x1uMGh3h
SSO is important for enterprise.. but github presents a challenge where devs usually have pre-existing personal accounts which are added to company github accounts, rather than the company account being used.
That's what people used to do before because there were no good options to provision separate work accounts for people. With the new for business model I'm guessing we'll see people being issued work accounts and keeping their personal GitHub accounts completely separate, which might be a good thing.
It makes sense to separate access ("this person has access to Example Corp's repos only as long as they work for Example Corp") from identity ("this person owns this account").
Introducing single-sign-on as one way to simplify login, and potentially as a second-factor for gaining access to repositories run by the business, makes sense. Making developers create entirely separate accounts doesn't.
I am happy that they continue to add features like this, but I feel like some of the more common wishlist items are not being addressed.