Skip to content

Commit 52f10ec

Browse files
authored
intro section added
1 parent 9974459 commit 52f10ec

1 file changed

Lines changed: 30 additions & 0 deletions

File tree

‎quick_github_tutorial.txt‎

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,36 @@ ISBN: 978-1-491-94974-0
77

88
you can find the book online.
99

10+
********** intro **********
11+
12+
git is a version control system,
13+
github is the web version of it.
14+
15+
16+
using github, you can see team progress, issues, branches,
17+
everything you need to manage a large scale software project.
18+
19+
in general, you will have three basic branches;
20+
-master branch: everything will be merged to this branch eventually
21+
-feature branch: for each feature, you may have a branch
22+
-release branch: all releases may have a separate branch, v1.0, v2.0 etc.
23+
24+
your team must have a branching strategy from the beginning of the project
25+
26+
every branch should have a README.md, where you put basic, introduction information about the branch.
27+
28+
commit history for a file will give you the list of commits, who did it and when.
29+
30+
issues list is to report bugs. team members should always keep an eye on the issues.
31+
32+
one of the most important views of a project is Network tab, where you can see all the branches and merges in the project life cycle.
33+
34+
members vs team; members who create a fork of the project. forking means on GitHub, you will have a copy of the project on your GitHub account, not on your local computer. however, teams are created to work on the project and commit their changes from their local repo to the remote repo.
35+
36+
WE ARE NOT GOING TO EDIT ANYTHING ON GITHUB,
37+
BUT WE WILL COMMIT ALL OUR CHANGES USING COMMAND LINE GIT COMMANDS.
38+
39+
1040
********** first time installation **********
1141

1242
1. Download and install GitHub to your computer (github.com)

0 commit comments

Comments
 (0)