Software's Soul - BSC

Why I needed to do it Lately I’ve dealt with an issue  on my project cordova broadcaster plugin I’ve fixed it, committed and published to NPM  the new release of plugin. I was happy for contribution and also because I had quickly answered to the request, but, after a while,  I received following comment on such issue: Changes look good. Fyi to reference an issue in a commit message you should use the syntax fixes #10 instead, so that the commit will actually be referenced in the issue feed. So … I forgotten to comment, in the right way, the related commit and I have already pushed all … damn! :-( Then I’ve started to search for a solution and “ googling ” I got a lot of results related to fix last commit using amendment (  — amend ). After a bit, finally, I found it on SuperUser and, once applied, the commit ’s comment is, magically updated in the right way. … Just one word: “Awesome”. So .. I would share with you the procedure...

Developer & Github For those like me who develop using Github and continuously evaluates new projects to fork them or to reuse in own development work every tool that could help us about that is welcomed During dayly blogs' screening,  my attention has been captured by a new Chrome Extension named Octotree  that display Github code in tree format . I've immediately installed it because often i deal with a lot of clicks to open source code and ... et voilà problem solved. Description  Display GitHub code in tree format. Useful for developers who frequently read source in GitHub and do not want to download or checkout too many repositories. Features  Easy-to-navigate code tree like IDEs Fast browsing with pjax Support private repositories  Conclusion Now i'm an  Octotree   happy user and i hope that this extension helps you as much as helped me