1. Orange skies.

2. Extremely expensive housing.

3. Can't go outside.

Mars? Nope, San Francisco.

You forgot the fourth point, Teslas everywhere.

Like many others, I use Github every day. Changes like this add friction to our workflow.

There better be a damn good reason for these changes, otherwise it's a pointless redesign that looks no better than it did previously while simultaneously adding a slight overhead as users "learn" the new layout.

Does anyone know of an option to revert this update?

My hypothesis is the point is to compete with Jira. That would be MS's biggest competitor in this space, and the changes make it look a whole lot more like that.

I wonder if MS has gone back on their word to leave GitHub to it's own devices...?

I have been unable to find a method to revert. Best option might be to make a bunch of noise. Other than that, it's migration time.

> My hypothesis is the point is to compete with Jira.

When they start making everything drag & droppable at a huge cost to UI latency and bundle size (plus, for some reason, idle resource use), we'll know for sure that's what they're doing.

If competing with Atlassian is the point, then they're going to have to completely revise their licensing model for a start. GHE is _far_ too expensive compared to Atlassian's whole software suite to be any real competition.

It gets merged into MS product catalog, GitHub might have a time table at this point...

just like Teams got marketshare

I'm curious, what exactly has broken in your workflow? The biggest issue I see is that you are unable to see build status on a commit (above the file list), but otherwise nothing really has changed too much in my opinion.

Some examples:

1. On larger monitors e.g. 4K the menus are on the far left whilst the content is in the middle which makes it far more of an effort to navigate around.

2. Row separators have disappeared so I have to be a lot more deliberate about which file I am clicking now since it's a lot easier to mis-click.

3. Buttons are a mess. You can't distinguish what is a button and what is not e.g. Clone versus the Open Issue label.

4. Clone button is so prominent. I only do this once per repo and yet it's like a giant CTA begging you to click it. Likewise for the folder icons. No need for them to be coloured.

Not discounting your experiences but I really have not found any of what you described as a problem.

Except for the very prominent clone button, I really have not felt it has brought anything negative.

Although, I probably use GitHub like 50% less than you.