GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
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
Mostly a personal preference, not sure how it affects overall performance
remove duplicate topic label
The first warning is short enough such that it wont wrap to the next line.
Hence the subsequent message does not need a topic label.
wrap message gracefully
eh, fine by me. it's basically just a matter of personal preference since i'm pretty sure we use both styles within the codebase already
I don't mind, but it might be worth not making changes that would muddy git blame
hmm, okay.. I'll use this PR to correct the typo and remove just the \n at towards the end of the file then.. k?
remove unnecessary modifications
Since jekyllbot doesn't squash and merge, I'll manually rebase once the new diff is approved..
Looks good after squash 👍
Good catch @ashmaroli 👍
@jekyllbot: merge +bug
Update history to reflect merge of #6229 [ci skip]
Well I'll be a....... JekyllBot does squash and merge.. Cool!
Thanks Frank 😃
I forgot about that 😜👍🏼