Skip to content
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

fix code style badge markdown #760

Closed
callmecavs opened this issue Jan 24, 2017 · 13 comments

Comments

@callmecavs
Copy link
Contributor

commented Jan 24, 2017

noticed in trying to add the code style badge (the shields.io one) to some of my READMEs that copy/pasting the code on the README doesn't work.

GitHub seems to get tripped up on the URL encoded space - replacing the %20 encode with an _ yields the same text, and fixes the badge embed.

Submitted a PR too: #761

@callmecavs callmecavs referenced this issue Jan 24, 2017
@yoshuawuyts

This comment has been minimized.

Copy link
Contributor

commented Jan 24, 2017

@feross feross closed this in 847ef63 Jan 24, 2017

feross added a commit that referenced this issue Jan 24, 2017

@feross

This comment has been minimized.

Copy link
Member

commented Jan 24, 2017

Thanks for the PR, merged it. I wasn't able to reproduce the issue, though. Maybe it was a transient issue? Can you check and see if %20 still causes problems for you?

@callmecavs

This comment has been minimized.

Copy link
Contributor Author

commented Jan 24, 2017

@yoshuawuyts @feross still seeing the problem on my end - also not seeing es6 work for codeblock highlighting on README's anymore (though javascript correctly highlights ES6 syntax now) either. noticed it around the same time as I noticed the badges issue

@feross

This comment has been minimized.

Copy link
Member

commented Jan 24, 2017

@callmecavs Do you have a link to a readme that exhibits the issue?

Sounds like they updated the version of https://github.com/github/markup ?

@feross feross reopened this Jan 24, 2017

@callmecavs

This comment has been minimized.

Copy link
Contributor Author

commented Jan 25, 2017

@feross highlighting is broken here, and code style badge broken here for me (incognito, no extensions)

agreed that it might be a markdown change - maybe a highlight.js version bump broke the syntax highlighting? i could see the es6 being deprecated/removed as it was stabilized and integrated into javascript. only like 50% sure github uses it tho

@dougwilson

This comment has been minimized.

Copy link

commented Jan 25, 2017

Many shields io badges have a space. I have been seeing over the past week at least github flipping between them broken and not broken. I assume this is a general github issue.

@callmecavs

This comment has been minimized.

Copy link
Contributor Author

commented Jan 25, 2017

@feross @dougwilson getting random 504's on some cached badges - looking at the choo repo again, now its the npm badge. could be related to GitHub caching, changing to an _ might just be busting the cache (not sure if chrome encodes the url before or after hitting enter)? likely not related to the standard badge I think we can say at this point

screen shot 2017-01-24 at 8 38 07 pm

@feross

This comment has been minimized.

Copy link
Member

commented Jan 25, 2017

I've reached out to GitHub support on Twitter. Closing this, as it's not a standard issue.

@feross feross closed this Jan 25, 2017

@feross

This comment has been minimized.

Copy link
Member

commented Jan 25, 2017

@callmecavs GitHub is asking if you can open an issue about this here http://git.io/c

@callmecavs

This comment has been minimized.

Copy link
Contributor Author

commented Jan 25, 2017

@feross i opened one yesterday when I pinged GitHub on twitter about it, ill submit another in a bit

@feross

This comment has been minimized.

Copy link
Member

commented Jan 25, 2017

No worries if you already opened an issue

@callmecavs

This comment has been minimized.

Copy link
Contributor Author

commented Jan 25, 2017

will let you known when i hear back

@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
4 participants
You can’t perform that action at this time.