↵

Ask DN: Let's talk about Git

over 8 years ago from Daniel Fosco, UX Designer

  • Daniel FoscoDaniel Fosco, over 8 years ago

    Thanks for the input!

    I think we're pretty much on the same page — I started using Sourcetree and have recently moved to the CLI. Also, agree on Github Client > Sourcetree > CLI.

    One of the roadblocks I see to start using Git is the mental model you have to wrap your head around, which makes total sense and becomes second-nature after a while, but can be hard to grasp in the beginning.

    Btw, do you tie your to-do lists to Github issues using commits? I haven't seen that much, and I'm not sure that's a common occurrence outside of large open-source projects that pretty much live on Github.

    1 point
    • Caleb SylvestCaleb Sylvest, over 8 years ago (edited over 8 years ago )

      The mental model of Git is tough to grasp for beginners. I remember my first day on a new job and I had never used Git. A guy printed out a paper for me to read and look at a flow chart, needless to say it made zero sense.

      Luckily there are now tons of resources for learning Git. Treehouse, CodeSchool, even Github has info for beginners.

      I do use Github issues and tie commits to the issues. We use this method at work quite often. You can do cool stuff like close issues with a commit, if you add something like "Fix #21" to you commit message, but we don't typically do this anymore because we want to QA the issue before closing. So instead (if I remember) I usually copy the commit number in Github and paste it into the issue, which creates a connection.

      1 point