Let’s say you want to work on some code in a git repository. To do this, generally you will “fork” this repository, by cloning it into your own repository. On GitHub there’s a simple “fork” feature that takes care of this. After a while, you might have made some changes, but the original repository that was forked might also have new commits pushed to it. A question many new git users then face is: “How do I pull the upstream changes from the original repository into my own?”
Review: WeBuilder 2014 in retrospect
A while back I made a post about the PasteLock service I’ve developed and published. It took me quite a while to develop the service, mainly due to the fact that I am not a webdesigner, I’m a webdeveloper. As such, I usually open up Adobe Dreamweaver to develop anything that requires HTML and CSS work. Why Dreamwaver? You must be cringing if you think I need a WYSIWYG editor to create a website. This is not the case, but I like to see what I develop when I develop it.
Unlike before I decided not to go with Dreamweaver for once and try something new. I came across a web development suite that seemed to meet all of my requirements. WeBuilder 2014, still in beta at the time, had all of the tools I needed, like syntax highlighting, extensive code completion, a live browser preview and even support for PHP debugging. As I was immediately won over by the extensive feature list, I decided to give it a try.