Why does the extension need to read the user's browsing history?

It isn't necessary for the button to be visible 100% of the time. Please either remove it altogether, or make it optional.

Hello! There are already separate folders for Firefox and userscripts. Would be nice to make one for the original source code too.

Looks like div.header-search-scope also forces 255, 255, 255 for text color.

Focused mode is fine though:

seems the original style override it.

Looks like the black bar is back 😕

Looks like Github changed their styling

Currently every page loads the dark header and then turns to light, causing a flash. It would be better if it could somehow avoid that.

The "Create new" button in the header is white when using the grey header.

Oh, back to the issue. It looks like someone sneezed on your camera lens.

Reproduce steps:

• Visit: https://github.com/DennisSnijder/MakeGithubGreatAgain
• Notice boogers all over the image. Gnarly.

I'd produce logs but my deep machine learning neural net on booger detection is in it's infancy. It keeps detecting a tree...

As Github changed the "dark-header" class.
The Firefox and Safari extensions are broken.

This needs to be fixed.

document-end does work though

The javascript seems to work great in Safari as well, would be nice with a packaged extension :)

Element's style left of the input box is broken.

stackoverflow changed from black to white, make it great again!

See this screenshot:

Just wanted to let people know that my extension is still being maintained and still works. I recently made some improvements to it so it works with the new code search feature preview.

Repo: https://github.com/stefansundin/github-light-navbar

Chrome Extension URL: https://chrome.google.com/webstore/detail/github-light-navbar/ghmhnieihpbnbakfplhabglpdpcphomf

That's all. Enjoy.

Handy script, would be neat if it applied to gist.github.com as well, I may try to make this when I'm home shortly :)

See title

Often Github's changes to CSS can break extensions like this one, but sometimes contributors will come out with a fix pretty soon.

It would be great to have someone who could quickly merge these kinds of fixes, so that users don't suffer a period of lost functionality.

However I appreciate it might be a little bit complicated, because the extension would also need to be pushed up to the Chrome Web Store.

I have no idea what is involved in that, or whether it is a task that can be easily shared. But if it could, that would be great!

PS: This issue's title was a short-lived topical reference.

I'm publishing your app to the chrome webstore.
let me know if you are against it, so I can remove.

Github just updated the header-dark class to be the default header class.
We need to overwrite the existing CSS class to get the extension working again.

Only Black Lives Matter！ 🏴 🖤

Currently, "This repository" label is blank and white. It is not the default blue bootstrap theme color. When inspected, the label element was missing the focus class.

Attached screenshot. At the top left, you can the see the white label without focus.

Here's an example:
https://github.com/trending/php

Hey could you push the 1.3.0 release to the chrome store? My body is ready for teh faster switching 😋

This extension works with absolutely zero changes in Firefox. Would be cool to make available to Firefox users too.

MakeGithubGreatAgain got bumped to 2.0.1 but the manifest.json still on 1.5.1

Hey

Just something that might be helpful towards this comment:

// Chrome doesn't have an easy way to broadcast a message to all
// content scripts, so just broadcast the message to every tab
// and rely on Chrome's manifest permission to restrict

You can totally do this with the chrome.runtime API 🎉

https://developer.chrome.com/extensions/runtime#method-sendMessage

It will be better if the original css file can be blocked.

Recently, the box on the dashboard containing the list of your repos has moved from the right of the page to the left of the page.

Things being as they are these days, I am not really against things moving from the right to the left.

But if enough people are bothered by this, I don't mind adding a float: right to restore things back how they were in 2016.

👍 = move those repos back over to the right. Restore balance to the desktop.
👎 = keep the repos where they are now. Keep those Github designers in a job.

This offer will expire 31st October 2018.

Unless headers-that-aren't-headers is the new style trend or something, this probably isn't what you were going for...

All you need is a good ol' space between your #s and your header text, and it should be just fine.

Since @mdo has completely lost the plot:

For now! Not trying to be a jerk, but that extra class will be going away
soon. Just how we shipped v1 of it.

It might be a good idea to implement a CSS solution, as the JavaScript solution
is likely to break. Here is one I came up with:

http://github.com/svnpenn/dotfiles/blob/cf47bf9/stylish/github.css#L2-L32

I think you need to save us from new github colors! Especially links!

I see the header-dark class toggling, but it looks like they've put the styles into the header class and removed the header-dark class altogether.

https://wiki.greasespot.net/Metadata_Block#.40downloadURL
https://wiki.greasespot.net/Metadata_Block#.40updateURL

Would probably also be a good idea to make a tag like stable and then point to the raw .user.js URL in said tag (eg. https://github.com/DennisSnijder/MakeGithubGreatAgain/raw/stable/MakeGithubGreatAgain.user.js) and then update the tag whenever making a new release and bumping the version.

Hi again, I think it would be a pretty nice feature if we can switch the theme black and white by click on the extension icon.

There's a straight-forward one here that can be made referencing the classic header color: "Make Github Gray Again"

Just saying... :)

The black bar is back... Again...