Gitting better

1.
Gitting Better

2.
Gitting Better kinda

3.
Hats Off Gitting Better Hello,World! Overview

4.
Hats Off Gitting Better Hello,World! Overview GittingBetter Hello,World!

6.
What Git is?

7.
What Git is? NOT

8.
Git is not... ...a convenient backup solution for your source code

9.
Git is not... ...a convenient backup solution for your source code but

10.
it

11.
is

12.
pretty

13.
good

14.
at

15.
it!

16.
:D

17.
Git is not... ...another pain in the ass you have to deal with

18.
Git is not... ...another pain in the ass you have to deal with but

19.
it

20.
is

21.
pretty

22.
good

23.
at

24.
it!

25.
:(

26.
What Git is... ...a distributed version control and source code management system.

27.
What Git is... ...a distributed version control and source code management system.

28.
First off, Gitis a version control system, a simple command line tool for keeping a history on the state of your source code projects. You use it as you might use something like Subversion, CVS or Perforce.

29.
First off, Gitis a version control system, a simple command line tool for keeping a history on the state of your source code projects. You use it as you might use something like Subversion, CVS or Perforce.

30.
First off, Gitis a version control system, a simple command line tool for keeping a history on the state of your source code projects. You use it as you might use something like Subversion, CVS or Perforce. “cli” snapshots,

31.
not

32.
diffs!

33.
Git allows groupsof people to work on the same documents (often code) at the same time, and without stepping on each other’s toes.

34.
Git allows groupsof people to work on the same documents (often code) at the same time, and without stepping on each other’s toes.

35.
Git allows groupsof people to work on the same documents (often code) at the same time, and without stepping on each other’s toes. NO

36.
MUTEX,

37.
YAY!

38.
You tell itto track ﬁles in your project and periodically commit the state of the project when you want a saved point. You can share that history with other developers for collaboration, merge between their work and yours, and compare or revert to previous versions of the project or individual ﬁles.

39.
You tell itto track ﬁles in your project and periodically commit the state of the project when you want a saved point. You can share that history with other developers for collaboration, merge between their work and yours, and compare or revert to previous versions of the project or individual ﬁles.

40.
Git is fullydistributed, which means that it can work almost entirely ofﬂine. In contrast toVCS tools like Perforce or Subversion, Git does nearly all of its operations without needing a network connection, including history viewing, difference viewing and commiting. This means that Git is very fast compared to other systems partially due to the fact that none of these operations has any dependency on network latency.

41.
Git is fullydistributed, which means that it can work almost entirely ofﬂine. In contrast toVCS tools like Perforce or Subversion, Git does nearly all of its operations without needing a network connection, including history viewing, difference viewing and commiting. This means that Git is very fast compared to other systems partially due to the fact that none of these operations has any dependency on network latency.

42.
Git is alsovery space efficient. It is even smaller than the Subversion checkout, which is pretty amazing, considering that the Git clone contains the entire history of the project — every version of every file back to the first commit, whereas the Subversion checkout is just the last version of the project.

43.
Git is alsovery space efficient. It is even smaller than the Subversion checkout, which is pretty amazing, considering that the Git clone contains the entire history of the project — every version of every file back to the first commit, whereas the Subversion checkout is just the last version of the project.

44.
Probably the mostcompelling feature of Git is Gits branching model. Instead of the popularVCS branching method of simply cloning into a separate directory for a branch, Git lets you switch between branches in a single working directory. Creating and switching between branches is nearly instant, not all of your branches need to be shared, and it’s easy to stash partially completed work.

45.
Probably the mostcompelling feature of Git is Gits branching model. Instead of the popularVCS branching method of simply cloning into a separate directory for a branch, Git lets you switch between branches in a single working directory. Creating and switching between branches is nearly instant, not all of your branches need to be shared, and it’s easy to stash partially completed work.

46.
Instead of onlyhaving branches for major development line departures, Git developers routinely create, merge and destroy multiple branches a week, or even per day. Often each feature or bug you are working on can have its own branch, merged in only when it is complete.This model allows you to experiment quickly, easily and safely - without having to go through hoops to get back to where you where. It enables and encourages a non- linear development cycle, where you can work on multiple lines of thought in parallel without them stepping on each other.

47.
Instead of onlyhaving branches for major development line departures, Git developers routinely create, merge and destroy multiple branches a week, or even per day. Often each feature or bug you are working on can have its own branch, merged in only when it is complete.This model allows you to experiment quickly, easily and safely - without having to go through hoops to get back to where you where. It enables and encourages a non- linear development cycle, where you can work on multiple lines of thought in parallel without them stepping on each other.

48.
As it isprimarily a command line tool, most of the examples in this course will show the command line versions of the functions.

49.
As it isprimarily a command line tool, most of the examples in this course will show the command line versions of the functions.

50.
As it isprimarily a command line tool, most of the examples in this course will show the command line versions of the functions. on

52.
Mac

53.
:D

54.
help conﬁg init add rm mv status commit log diff show branch checkout merge tag clone fetch pull push remote stash clean reset rebase bisect grep reﬂog

55.
help conﬁg init add rm mv status commit log diff show branch checkout merge tag clone fetch pull push remote stash clean reset rebase bisect grep reﬂog

56.
help conﬁg init add rm mv status commit log diff show branch checkout merge tag clone fetch pull push remote stash clean reset rebase bisect grep reﬂog Getting

57.
Started

58.
help conﬁg init add rm mv status commit log diff show branch checkout merge tag clone fetch pull push remote stash clean reset rebase bisect grep reﬂog Basic

59.
stuff

60.
help conﬁg init add rm mv status commit log diff show branch checkout merge tag clone fetch pull push remote stash clean reset rebase bisect grep reﬂog History

61.
help conﬁg init add rm mv status commit log diff show branch checkout merge tag clone fetch pull push remote stash clean reset rebase bisect grep reﬂog Branching!

62.
help conﬁg init add rm mv status commit log diff show branch checkout merge tag clone fetch pull push remote stash clean reset rebase bisect grep reﬂog Remote

63.
(HUH?)

64.
help conﬁg init add rm mv status commit log diff show branch checkout merge tag clone fetch pull push remote stash clean reset rebase bisect grep reﬂog advanced

65.
stuff

66.
help conﬁg init add rm mv status commit log diff show branch checkout merge tag clone fetch pull push remote

67.
Getting Started help conﬁg

68.
$ git helpverb $ git verb --help Display

69.
“HELP!”

70.
information

71.
about

72.
Git

73.
demo

74.
$ git config--system key value $ git config --global key value $ git config --local key value Get

75.
and

76.
set

77.
repository

78.
or

79.
global

80.
options

81.
$ git config--system key value $ git config --global key value $ git config --local key value default!

82.
$ git config--global user.name “John Doe” $ git config --global user.email “johndoe@example.com”

83.
demo

84.
Basic Commands init, add,rm, mv, status commit

86.
Working

87.
Copy

88.
Repository

92.
$ git init Create

93.
an

94.
empty

95.
git

96.
repository

97.
$ git init

98.
$ git init

99.
$ git init Repository Working

100.
Copy

101.
$ git init $git init

102.
Central

103.
Repository

106.
demo

107.
$ git addfiles Add

108.
new

109.
or

110.
modified

111.
files

112.
to

113.
the

114.
staging

115.
area

116.
$ git addfiles Add

117.
new

118.
or

119.
modified

120.
files

121.
to

122.
the

123.
staging

124.
area

125.
$ git addfiles Add

126.
new

127.
or

128.
modified

129.
files

130.
to

131.
the

132.
staging

133.
area (a.k.a.

134.
“index”

135.
or

136.
“cache”)

137.
Now Pay Attention! TheThree States

138.
This is themain thing to remember about Git if you want the rest of your learning process to go smoothly. Git has three main states that your ﬁles can reside in: committed, modiﬁed, and staged.

139.
This is themain thing to remember about Git if you want the rest of your learning process to go smoothly. Git has three main states that your ﬁles can reside in: committed, modiﬁed, and staged. 1 2 3

140.
Committed means thatthe data is safely stored in your local database. Modified means that you have changed the file but have not committed it to your database yet. Staged means that you have marked a modified file in its current version to go into your next commit snapshot.

141.

142.

143.

144.

145.
Staging Area

146.
Staging Area Stage ﬁles

147.
Staging Area Stage ﬁles Commit

148.
Working Copy StagingArea Repository git add$ Add

149.
new

150.
or

151.
modified

152.
files

153.
to

154.
the

155.
staging

156.
area files

157.
Remove

158.
files

159.
from

160.
the

161.
working

162.
directory and

163.
staging

164.
area git rm$ files WorkingCopy Staging Area Repository

165.
Move

166.
or

167.
rename

168.
a

169.
file,

170.
or

171.
a

172.
directory git mv$ sourcedestination Working Copy Staging Area Repository

173.
demo

174.
$ git status Show

175.
the

176.
status

177.
of

178.
the

179.
working

180.
directory and

181.
staging

182.
area

183.
demo

Gitting better

More Related Content

What's hot

Viewers also liked

Similar to Gitting better

Recently uploaded

Gitting better