[Go] 7 tips for git beginners

This article transferred from: http://www.open-open.com/news/view/b7227e

Read Catalogue

• First: Take the time to learn basic Git operations
• Article two: Start with a simple Git workflow
• Fourth: Understanding Branching concepts
• Fifth: Learning Staging Area

English Original: 7 useful Git Tips for beginners

When I first started using Git version control, I wasn't sure if I'd pay that much time. Branch, Stage, Stash, these Git nouns are very unfamiliar to me.

And today I can't imagine what it would be like to live without Git. Git not only provides the version control I really need, but also makes me a better programmer.

Here are a number of tips to help you make Git a very important part of your development effort.

First: Take the time to learn basic Git operations

The basic thing about learning Git is not asking you to read the entire Git document from start to finish (but if that's your way, I wouldn't oppose it).

There's too much education in Git, and I'm sure there must be the best way to learn about your appetite.

Check out these Git learning resources below:

• How to get started with Git quickly
• Try a Git-15 minute Git interactive tutorial
• Tips and Tricks (Ry's git teachings) are a practical tutorial on common git features
• Git Simple Guide
• Git ready is a site that has many simple and short git hints.
• Git Cheat Code
• The Git Tower learning area is a list of git learning resources on my Site
• Git Official Tutorials
• Training:git Basics (VIDEO) is a list of videos on YouTube
• Pro git is an online book that gives you a deep understanding of git

Go back to the top second: start with a simple Git workflow

Less is more.

Often, Git is associated with a complex workflow. But I can say this: you don't have to be a git guru for a while for the benefits of Git.

Git workflows can be very simple-and in many cases you need to be so simple. You can certainly use multiple remote repositories, issue pull request, rebase changes and so on, but you don't want to use these words completely.

Getting from a simple workflow to a hand also makes it easy to add complexity later or use Git advanced features. When you need to use these features, Git is ready.

Here are some examples of different Git workflows that you can get inspired by their ideas

• The designer's Git workflow
• Markus Prinz Git Workflow
• Yehuda Katz's Common Git workflow
• A Git workflow for Agile teams

Overall: Don't get stressed out because you think git is going to learn everything, you can start using git today.

Article three: Don't be afraid to make mistakes again

One of the best things about Git is that it's almost 100% easy to get started.

Keep in mind that the following points will make you sleep more soundly at night:

1. Git basically doesn't delete data. Even those actions that appear to be deleting data are actually intended to allow you to undo the deletion faster and to add data to the system.
2. Git basically can undo all the actions. I encourage you to experiment more and explore your ideas, as this is one of the main benefits of using a version control system system.
3. Each member of your team has his or her own copy of the computer. Essentially it's more like a redundant backup of the entire version control project (including the entire history), you poke big Lou Zi and there's no way to restore the situation is extremely rare.

Go back to the top fourth article: Understanding Branching Concepts

In Git, the concept of branching is the most useful thing you can learn from the beginning. Branching allows you to isolate the development of your project, and it is critical to be an efficient Git user.

It doesn't sound like a big deal at first, but once you fully understand the branching concept, you'll start thinking about how you're going to survive without it.

While other version control systems use branching concepts, Git is the first system to implement it and make it useful.

Here are some resources to help you understand the Git branching concept:

• Learngitbranching! is an interactive tutorial for a Git branch
• Git Basic Branch and merge
• Branching is a short introduction to Git branching and merging
• Git branch is a git tutorial with a lot of drawings
• A mature Git branching model

Go back to the top fifth article: Learn staging Area

Versioning can be very useful when your submission contains only a few related changes [b], which ensures that your submissions are rolled back without any side effects, and that the habit of submitting often allows your coworkers to better understand your progress.

Git has a feature called staging area that makes it all possible.

Learn to use staging area and fall in love with it because this is the most important and independent module in Git.

1. Why staging area so useful?
2. What are the benefits of using staging area--a discussion topic about Git Staging Area
3. Ah ha! The time to learn Git--a blog post
4. A short tutorial on staging area on Git

Sixth: Using the Git graphical interface

Although using a graphical interface is definitely not a requirement, I highly recommend it.

Using a graphical interface makes most operations simple, giving you the edge at the start of your project.

In any case, using Git should not just remember a variety of commands and parameters, but rather improve your programming workflow. If the graphical interface can do this, there is no reason to make the simple work difficult.

Check out these Git interfaces:

• Open source Git graphical interface under Tortoise Git-windows platform
• GITX (L)-Open source Git client under Mac OS X
• Free Git or Mecurial interface under Sourcetree-windows and MAC
• Git-cola-an open source Git interface
• Tower-Our company's Git interface for MAC users

Using a graphical interface does not relieve you of the burden of learning git basics, but once you have conquered git happily, using these tools will make your life easier.

Seventh: Promise yourself you'll use Git

Using a new tool starts with a headache, and there's only one way to get through this learning curve: keep going.

Make a full commitment, don't look back. Introducing Git into your normal workflow will soon prove to be the biggest, most meaningful decision you've made in the near future.

Avoid this: "I'm going to use Git in this project, but the other items are going to be the same." "At least not at first."

A full commitment to this mindset will give you more opportunities to practice and make things easier because you know that you now have a version control system in the project. And more importantly, let Git be your programming habit.

In the near future, you'll see that there are only a few situations where you don't need Git,

Make a 100% commitment to yourself as the beginning of the path to Git conquest.

Bole Online-Wu Pengyu translation Link: http://blog.jobbole.com/50603/

[Go] 7 tips for git beginners