Posts Tagged: git

Time has passed… In commit messages, describe intent rather than implementation details. (thanks Remco!) Using github? Then you can refer to issues in your commit messages using #. Ie when there is an issue (#12), and you want to fix it. Just refer to it with a #12 and Github will automatically link your commit to the issue. It always takes more time then you always think to revamp your project(s). Start with why. Easier said then done though. (Reading the book, so I might write a review about that soon) Paypal’s functionality to change your password… Read Article →

Another week has passed: Unlike in Windows; in Chrome you cannot easily focus on your bookmarks bar with a keyboard short key on Mac OS X. If you want to run rake tasks in your specs in a before block, be sure to set a line[code language=”ruby”]Rake::Task[name].reenable[/code] so you can re-execute them every time. Rake seems to remember which task has been executed, so you cannot execute it twice. If you want to stub out STDOUT messages (like with ‘puts’) in your spec, use:[code language=”ruby”]STDOUT.stubs(:puts)[/code] When in doubt, speak up. Always. With Scrum, big stories… Read Article →

Got this via a friend and had to share this with you… Ever heard of Bumblebee? Well I thought it was about this guy: Apparently it wasn’t, in this case. In fact, I still don’t even know what piece of software it is, but I do know about one of its most famous commits on github now. This commit is very small, yet makes a very big difference for the user… If you want to have a laugh see the commit yourself, and then all the comments, they are hilarous. Ok, one teaser: Still reading…?

I was looking for a way to easily print the current gemset I am in when working in the terminal. I found a stack overflow post, but it did not really satisfy me. With some googling I also found this post. I modified the script a tiny bit (color preferences + added __git_ps1 to detect branch) and would like to share you what I’ve got. This is the complete script I use now, copy & paste if you like. The result looks like this: [sourcecode] # This shows the git branch of the current directory… Read Article →

Recently someone is helping me out on my Dune II – The Maker project. He works with GIT, a version control system like SVN. I don’t care about the differences between them at this point, except for one difference: The patch files. So here is the situation: Someone works with GIT, makes some changes and creates a patch file out of them. He sends it to me so I can apply it to my SVN repository. In theory, I thought, this would work fine. Atleast I think the possibility to share patches among different versioning… Read Article →

Scroll To Top