19 ms·
Even better than making this blog post would have been to make a pull request to the public repo that runs the site (https://github.com/resume/resume.github.com
by crcastle 14y ago
Even better than making this blog post would have been to make a pull request to the public repo that runs the site (https://github.com/resume/resume.github.com https://github.com/resume/resume.github.com). It's written in JavaScript. Seeing as you're (http://resume.github.com/?beezee http://resume.github.com/?beezee) not only an experienced github user but also an experience javascripter, I would guess that it's well within your capabilities.
See a problem in the world? Fix it. Especially when it's trivial based on your skill set!
- beezee 14y agoAll about this but when I see 2 year old issues on a repo with code attached that have not been answered, I generally don't hold out high enough hopes of getting a response to justify forking cloning editing pushing and opening a pull request. At least with the blog post I had a chance to rally enough attention to make it the maintainers best interest to fix.
- crcastle 14y agoGood point regarding the chance to rally attention, but it would have been awesome to do both. It's probably 5-10 minutes of work to do the pull request!
- beezee 14y agoI can't disagree with you there - while I did spend some time in the Chrome debugger to see if I could find some clues, at the end of the day I'm stingy with my time when it comes to pull requests, largely based on the # of open issues on the repo. Maybe I'm jaded but after losing a few hours to pull requests that never went answered and reading multiple different takes on github etiquette, I tend to play that safely.