This is something I've had to do quite a few times, but it wasn't until I worked on a bunch of Github projects at HBO that I really started to get understanding branching in git. In my own Github projects I would often work right out of the master branch. This is fine for developers who are just getting started with git, but when working on large, enterprise projects you really want to be smart about using branches. This post will help you understand making git branches off of existing branches.
Last night I went to the "GothamSASS" meetup group event at the ThoughtWorks NYC office (which is awesome by the way) which was about Visual Regression testing.
Before, I was making my directory structures way more complicated then they needed to be. I had a main "git repositories" folder, and then inside of that I would use mkdir to create a new folder for each project. Then I would cd inside of that and run:
If you are going to be doing a lot of work in a command prompt you then you should enjoy it. It should be easy to read in terms of size and colors. It should be practical and functional but still show off your own style.
I'm a front-end developer, and I have a lot of source code in various repositories on github. The code is public and open source so it's free for me to just leave the code there and create as many repositories as I need. Actually hosting a website is much different from storing source code, but wouldn't it be nice if you could just have github also just host the dist files for your site as well? Well, it turns out you can! The best part is that this basically allows you to host unlimited open source websites and web apps for free with the simple and familiar (to me, at least) interface of git and github. Below is an example of how I've been doing this.
The posts on this site are written and maintained by Jim Lynch. About Jim...