I had to fork and patch a Node program last week as it was exhibiting some bad performance characteristics on Windows due to an unstable node FS feature (chokidar, for anyone interested, and it was down to fs.watch vs fs.watchFile whose performance and stability varies by platform).
As part of this, I realised that while I could hack the built code in my npm repo, I’d A) never forked code before and B) didn’t know how to test my changes i.e. get a package.json pointing at my forked code, and C) actually do a pull request.
Turns out it’s quite easy! The post on debuggable linked just above walks you through forking it, and the pull request process was fairly easy following the Github Using Pull Requests doc.
One thing I did differently was to not use the commit # in my package.json for testing, and instead used ”chokidar”: “https://github.com/alextreppass/chokidar/tarball/master”
The only thing I didn’t do properly, and the msysgit Windows UI hadn’t told me about, was setting my username and email so that Github would alias it to me on the pull request’s page. Command-line git moaned at me with a suggestion on how to fix it; here’s a page on how to set your username and email in the git config.
The recent revelations by the whistleblower Edward Snowden were fascinating. But they - and all the reactions to them - had one enormous assumption at their heart. That the spies know what they are doing. But when you look at the history of MI5 the astonishing thing is they never seem to know what…