-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
1008 lines (841 loc) · 39.9 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!doctype html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
<title>Version Control System With Git</title>
<link rel="stylesheet" href="css/reveal.css">
<link rel="stylesheet" href="css/theme/black.css">
<!-- Theme used for syntax highlighting of code -->
<link rel="stylesheet" href="lib/css/zenburn.css">
<link rel="stylesheet" href="overwrite.css"/>
<!-- Printing and PDF exports -->
<script>
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = window.location.search.match( /print-pdf/gi ) ? 'css/print/pdf.css' : 'css/print/paper.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
</script>
</head>
<body>
<div class="reveal">
<div class="slides">
<section>
<section>
<header> <u> About Me </u> </header>
<ul>
<li>My name is Victory Osikwemhe</li>
<li>Student of Accounting Department</li>
<li>Linux Evangelist</li>
<li>Shell Programming Nerd</li>
<li>Commandline Interface junkie</li>
<li>I mostly programme in Javascript and C </li>
<li>Addicted to coding for the past 7 years now </li>
<li>Unrepented Talkative </li>
</ul>
</section>
</section>
<section>
<section><header> What is this talk all about ? </header></section>
<section>
<p> Version Control System With </p>
<p> Git </p>
</section>
</section>
<section>
<section> Version control is all about keeping track of changes that has been made in a file or set of files </section>
<section> Version control systems, has to do with those tools that eases the pain of version control </section>
</section>
<section>
<section>
<header> <u> Types of Version Control Systems </u> </header>
<ul>
<li>Centralized Version Control System ( CVCS ) </li>
<li>Decentralized/Distributed Version Control System ( DVCS )</li>
</ul>
</section>
</section>
<section>
<section>
<header> <u> Centralized Version Control System </u> </header>
<ul class="git-cvcs">
<li>Only authorized users are allowed to work on the repository</li>
<li>Repository is located on only one machine</li>
<li>Often, internet connection is needed to work with the repository</li>
<li>It becomes unreliable as the number of users who have access to the repository increase</li>
<li>If the server crashes, it might lead to permanent loss of files if there is no backup</li>
</ul>
</section>
<section data-background-image="cvcs.png" data-background-size="contain"></section>
<section>
<header> <u>Centralized Version Control System Tools</u> </header>
<ul>
<li>Svn ( Subversion ) </li>
<li>CVS</li>
</ul>
</section>
</section>
<section>
<section>
<header> <u> Distributed/Decentralized Version Control System </u> </header>
<ul class="git-cvcs">
<li>Repository is not located on a single server</li>
<li>Network connection is not needed to work on the version controlled project</li>
<li>Increase in number of users working on the project does not ave a negative effect on latency , since everything been done is carried on the host computer</li>
<li>Everyone working on a project have a copy of the repository, backing up is not a problem</li>
</ul>
</section>
<section data-background-image="dvcs.png" data-background-size="contain">
</section>
<section>
<header> <u> Distributed/Decentralized Version Control System Tools</u> </header>
<ul>
<li>Git ( A.K.A The stupid content tracker )</li>
<li>Mercurial</li>
<li>Bazaar</li>
<li>Darcs</li>
</ul>
</section>
</section>
<section>
<section>
<header> <u> Let's talk about Git </u> </header>
<ul>
<li>Git is prounounced as Geet not jit </li>
<li>Git is not the short form of GITHUB</li>
<li>Git is generally known as the stupid content tracker</li>
<li>Git was actually created by Linus Torvalds to manage the linux kernel ( 2005 )</li>
<li>Git is currently maintained by Junio C Hamano</li>
<li>Git is a distributed version control system tool</li>
</ul>
</section>
<section data-background-image="torvalds.jpg" data-background-size="contain"></section>
</section>
<section>
<header> <u> Terminlogies in Git YOU MUST BE FAMILIAR WITH</u> </header>
<ul>
<li>Working Directory</li>
<li>Repository</li>
<li>Staging/Index Area</li>
<li>Commit</li>
<li>Branching</li>
</ul>
</section>
<section>
<header id="working-directory"> <u> Working Directory </u> </header>
<p> A working directory is a directory been currently version controlled </p>
<section data-markdown>
```bash
$~/my_project: ls
file1.txt ---------
file2.txt \_ # Files currently been tracked
file3.txt / # for changes by git
file4.txt --------
$~/my_project: pwd
my_project ------ # The working directory that
# contains files been version controlled
```
</section>
</section>
<section>
<section>
<header id="repository"> <u> Repository </u> </header>
<p>A magical location where version controlled contents are stored</p>
</section>
<section>
<header> <u>Local Repository</u> </header>
<p>This are repository that exits within the host computer</p>
</section>
<section>
<header> <u>Remote Repository</u> </header>
<p>This are repository that does not exists on the host computer</p>
<p>Often, network connection is required to connect to this repository</p>
</section>
</section>
<section>
<header> <u>Staging / Index Area</u> </header>
<p>Tracked contents are placed in this area before been saved ( or <a href="#commit">committed</a> ) to the repository</p>
</section>
<section>
<header id="commit"> <u>Commit</u> </header>
<p>Commit have to do with saving the changes that occur in the <a href="#working-directory"> working directory </a> </p>
</section>
<section>
<header id="branch"> <u>Branching</u> </header>
<p>This have to do with creating an entire development path</p>
</section>
<section>
<section data-markdown>
### Initializing a git repository
To initialize a git repository is to tell git to recognize the [working directory](#working-directory)
to be version controlled as a git repository
* `git init`
* `git init repo_path`
</section>
<section data-markdown>
```bash
$ mkdir git_project # create git_project directory
$ cd git_project # move into git_project directory
$~/git_project: ls # list all the files in directory
$~/git_project: pwd # present working directory
~/git_project
$~/git_project: git init # tell git about this directory
$~/git_project: ls -a
.git # where all the magic happens
```
</section>
</section>
<section>
<section data-markdown>
### Tracking a file
Whenever a new file is created, git does not know anything about this file, until you
tell it to start tracking this file.
* `git add`
</section>
<section data-markdown>
```bash
$~/git_project: git status # state of the working tree
On branch master
...
Untracked files:
...
list of files not tracked
$~/git_project: git add file_name # start tracking this file
```
</section>
<section data-markdown>
```bash
$~/git_project: git status # state of the working tree
On branch master
No commits yet
Changes to be commited
new file: file_name # staging area
```
</section>
</section>
<section>
<section data-markdown>
### [Commiting](#Commit) Changes
This have to do with telling git to send the tracked content in the staging area
to the [repository](#repository)
* `git commit`
</section>
<section data-markdown>
```bash
$~/git_project: git commit --message="message to annoate this commit with"
[master (root-commit) ...] annotated message
file changed, insertion made
create mod 100644 file_name
```
</section>
</section>
<section>
<section data-markdown>
### Commits logs
With git you can also view all commits logs.
Commits logs shows you a detailed information about the commits you and other developers have made
* `git log`
</section>
<section data-markdown>
```bash
$~/git_project: git log
commit sha1sum ( HEAD -> master )
Author: ...
Date: ...
commit message
```
</section>
<section data-markdown>
### Minimal Commit log
You can also tell git to show a minimal version of the `git log` output
```bash
$~/git_project: git log --oneline
shorten sha1sum
```
```bash
$~/git_project: git log -3
```
</section>
<section data-markdown>
### Search the log base on some criteria
You can also search the commit log base on some criterias like
* Author Name
* Committer Name
* Date of Commit
* greping for contents
* e.t.c
</section>
<section data-markdown>
### Searching by Authors Name
```bash
$~/git_project: git log --author="John Doe"
commit sha1sum ( HEAD pointer )
Author:
Date:
commit message
```
</section>
<section data-markdown>
### Searching by Committers Name
```bash
$~/git_project: git log --commiter="Jane Doe"
commit sha1sum ( HEAD pointer )
Author:
Date:
commit message
```
</section>
<section data-markdown>
### Date of Commit
```bash
$~/git_project: git log --since="2 hours ago"
commit sha1sum ( HEAD pointer )
Author:
Date:
commit message
```
</section>
<section data-markdown>
### Greping for contents
```bash
$~/git_project: git log --grep="Initial commit"
```
</section>
</section>
<section>
<section data-markdown>
### [Branch](#branch)
With branching you can create a different development path without messing up a stable branch. Branching is normally used to test out things that might
work or might not work.
* `git branch`
* `git checkout -b`
</section>
<section data-markdown>
```bash
$~/git_project: git branch --list # list all branches
* master # current branch
$~/git_project: git branch my_branch # new branch
$~/git_project: git branch --list
* master # current branch
new_branch_name # newly created branch
```
</section>
<section data-markdown>
### Moving into new branches
To start working with the new branch you have to tell git to move away from the current branch
( master ) to the newly created branch. Any changes made in the newly created branch won't show up
in the master branch. Moving into a new branch in git is called ***checkout***
</section>
<section data-markdown>
*** Before Checking out to a new branch ***
```bash
$~/git_project: git status
On branch master
....
```
*** move into new branch ***
```bash
$~/git_project: git checkout my_branch # move into new branch
```
*** After Checking out to new branch ***
```bash
$~/git_project: git status
On branch my_branch
...
```
</section>
<section data-markdown>
### Making commits in new branch
Commits in new branch will not be visible to other branches
```bash
$~/git_project: git add file_name
$~/git_project: git status
On branch my_branch
Changes not staged for commit:
...
...
modified: file_name
$~/git_project: git commit --message="commit message"
```
</section>
</section>
<section>
<section data-markdown>
### Checking the difference between two branches
Two branches in a single repository can have different development path
the difference between this branches can be checked
* ` git diff `
</section>
<section data-markdown>
```bash
$~/git_project: git diff my_branch master
...
--- a/file_name
+++ b/file_name
@@@ -1 +1 @@ # -1 means one line was removed, +1 was line inserted
- removed contents are marked with '-'
+ added contents are marked with '+'
```
</section>
</section>
<section>
<section data-markdown>
### Merging two branches
In merging, git actually only copies commits not present in one branch
and apply's those commits into the current branch
* ` git merge `
</section>
<section data-markdown>
```bash
$~/git_project: git checkout master # move into master branch
$~/git_project: git status
On branch master
....
$~/git_project: git merge my_branch # incorporates commits that are in my_branch and not in master branch
```
</section>
</section>
<section>
<section data-markdown>
### Deleting a branch
In situation wereby you no longer need a branch, it is advisable to delete the branch,
but you should make sure you have merged the commits made in that branch to a longelived branch
```bash
$~/git_project: git branch short_lived_branch
$~/git_project: git branch --list
* master
...
short_lived_branch
$~/git_project: git branch -D short_lived_branch
$~/git_project: git branch --list
```
</section>
</section>
<section>
<section data-markdown>
### Using a remote repository
Remote repository enhances collaboration
```bash
$~/git_project: git remote add origin https://remote_repo_url.com/project_name # adds the url as a remote repo
$~/git_project: git remote show origin -n
```
*** pushing to remote repository ***
```bash
$~/git_project: git push origin master
...
...
....
To /remote/repo/name
...
```
</section>
<section data-markdown>
### Pulling commits from a remote repository
Commits can be pulled from a remote repository in situations were a collaborator updates
the remote repo, they will be need for other collaborators to pull those changes from the remote repo
to their own local repo
```bash
$~/git_project: git pull origin master
...
...
...
from /remote/repo/name
```
</section>
<section data-markdown>
### Deleting a remote branch
If a remote branch is no longer needed, it is advisable you delete it, but you have to make sure
that all the commits in the remote repo is already pulled into the local repo
```bash
$~/git_project: git branch --remotes
all remote branch will be listed here
$~/git_project: git push origin :branch_name
To /repository/url
- [deleted] branch name
```
</section>
</section>
<section>
<section>
<header> <u>Undoing Changes</u> </header>
<img data-src="undo.jpg"/>
</section>
</section>
<section>
<section data-markdown>
### Reseting Changes
Reset helps you to revert back to previous commits.
Resets can be of three types
`git reset`
* soft
* mixed
* hard
* merge
* keep
</section>
<section data-markdown>
### Soft resets
Soft resets only moves the `HEAD` pointer to a previous commit.
* Staging area is not affected
* Working directory/tree is unaffected
```bash
$~/git_project: git status
On branch master
....
Changes to be committed:
file1.txt
file2.txt
```
</section>
<section data-markdown>
```bash
$~/git_project: git log
commit abcdef
...
commit one
commit 123456
...
commit two
commit abcd124
...
commit three
```
</section>
<section data-markdown>
```bash
$~/git_project: git reset --soft HEAD^
$~/git_project: git log
commit 123456
...
commit two
commit abcd124
...
commit three
$~/git_project: git status
On branch master
....
Changes to be committed:
file1.txt
file2.txt
```
</section>
<section data-markdown>
### Mixed reset
It moves the HEAD pointer to a previous commit without affecting the working tree.
A mixed reset only affects the HEAD pointer and the staging area. It affects the staging area
by unstaging all staged files
```bash
$~/git_project: git status
On branch master
...
Changes to be committed:
files1.txt
files2.txt
$~/git_project: git log
commit abcdef
...
commit one
commit 123456
...
commit two
commit abcd124
...
commit three
```
</section>
<section data-markdown>
```bash
$~/git_project: git reset --mixed HEAD^
$~/git_project: git log
commit 123456
...
commit two
commit abcd124
...
commit three
```
```bash
$~/git_project: git status
On branch master
...
Changes not staged for commit:
...
file1.txt
file2.txt
```
</section>
<section data-markdown>
### Hard Reset
Hard reset changes the working tree, unstages staged file, and moves the HEAD pointer
to a previous commit. Uncommited changes in the working tree goes missing ( permanently )
[]()
</section>
<section data-markdown>
```bash
$~/git_project: git reset --hard HEAD^
```
</section>
</section>
<section>
<section data-markdown>
### Unstaging a staged file
Unstaging a content removes that content from the staging area, the content
will not be represented in any further committs untill it is added back to the staging area
```bash
$~/git_project: git reset HEAD -- file_name
```
</section>
</section>
<section>
<section data-markdown>
### Changing the content of a file
The content of a file can also be changed to represent what it was as of the last time
it was committed
```bash
$~/git_project: git checkout -- file_name
```
</section>
</section>
<section>
<section data-markdown>
### Reverting a Commit
Reverting a commit is actually carried out when you want to revert the changes a commit introduces
and it does that with a new commit message
* `git revert`
```bash
$~/git_project: echo "First Commit" > file.txt
$~/git_project: git add file.txt
$~/git_project: git commit --message="First Commit"
$~/git_project: echo "Second Commit" > file.txt
$~/git_project: git add file.txt
$~/git_project: git commit --message="Second Commit"
$~/git_project: git log --oneline
sha1sum ( HEAD -> master ) Second Commit
sha1sum First Commit
$~/git_project: git revert HEAD
[master 9251901] Commit Message
....
```
</section>
</section>
<section>
<section data-markdown>
### Using Reflog to undo changes
Reflog records all changes that occur in a branch. With reflog it is easy
to undo an action
* `git reflog`
</section>
<section data-markdown>
### Using reflog to undo a soft reset
```bash
$~/git_project: git log --oneline
sha1sum ( HEAD -> master) third commit
sha1sum second commit
sha1sum first commit
sha1sum initial commit
$~/git_project: git reset --soft HEAD~2
$~/git_project: git log
sha1sum ( HEAD -> master ) first commit
sha1sum initial commit
$~/git_project: git reflog
sha1sum HEAD@{0}: reset: moving HEAD to HEAD~2
sha1sum HEAD@{1}: commit: third
sha1sum HEAD@{2}: commit: second
sha1sum ( HEAD -> master ) HEAD@{3}: commit (initial): Intial commit
$~/git_project: git reset --soft HEAD@{1}
$~/git_project: git log
sha1sum ( HEAD -> master) third commit
sha1sum second commit
sha1sum first commit
sha1sum initial commit
```
</section>
<section data-markdown>
### Undeleting a deleted branch
```bash
$~/git_project: git branch --list
* master
my_branch
$~/git_project: git branch -D my_branch
$~/git_project: git branch --list
* master
$~/git_project: git reflog
...
...
45b7b49 HEAD@{1}: commit: commit message
$~/git_project: git checkout -b my_branch HEAD@{1}
```
</section>
</section>
<section>
<section data-markdown>
### What Files is git tracking
* `git ls-files`
```bash
$~/git_project: git ls-files
file1.txt
file2.txt
file3.txt
file4.txt
```
</section>
<section data-markdown>
### Untracking a file
* `git rm`
```bash
$~/git_project: git rm --cached file1.txt
$~/git_project: git ls-files
file2.txt
file3.txt
file4.txt
$~/git_project: git status
...
...
...
Untracked Files:
file1.txt
```
</section>
<section>
<header><u>Making Git to shutup about untracked files</u></header>
<img height="400" data-src="shutup.jpeg" />
</section>
<section>
<p>You can tell git to stop showing you changes in a file and/or files that are currently untracked</p>
<p data-markdown> * `.gitignore` </p>
<div data-markdown>
```bash
$~/git_project: nano .gitignore
file1.txt
file2.txt
$~/git_project: git add .gitignore
$~/git_project: git commit --message="ignored some files"
```
</div>
</section>
</section>
<section>
<section data-markdown>
### Cloning a repository
Cloning a repository has to do with telling git to go to a remote repository get all the commits of that repository
and make a local copy of the repository on your machine
* `git clone https://repository_url`
```bash
$~/git_project: git clone https://github.com/git/git
```
</section>
</section>
<section>
<header> <u>DEMO</u> </header>
<img data-src="demo.jpeg"/>
</section>
<section>
<section>
<header> <u> GIT GUI ( moving away from the terminal ) </u> </header>
<img height="400" data-src="commandline.jpeg"/>
</section>
</section>
<section>
<header> <u> RESOURCES </u> </header>
<section>
<p> DOWNLOAD GIT </p>
<ul>
<li>
<a href="https://git-scm.com/"> Download Git ( all platforms executable )</a>
</li>
<li>
<a data-markdown> `apt-get update && apt-get install git ` ( commandline for linux ) </a>
</li>
<li>
<a href="https://git-scm.com/downloads/guis"> Git Gui clients </a>
</li>
</ul>
</section>
<section>
<p> BOOKS </p>
<ul>
<li>
<a href="https://git-scm.com/book/"> Pro Git ( Official book on git ) </a>
</li>
<li>
<a href="https://www.manning.com/books/learn-git-in-a-month-of-lunches">Learn git in month of lunches</a>
</li>
<li>
<a href="https://www.manning.com/books/git-in-practice">Git in Practice</a>
</li>
</ul>
</section>
<section>
<header> <u> Videos </u> </header>
<ul class="resource-links">
<li>
<a href="https://www.youtube.com/playlist?list=PL4cUxeGkcC9goXbgTDQ0n_4TBzOO0ocPR">Net Ninja</a>
</li>
<li>
<a href="https://www.youtube.com/watch?v=HVsySz-h9r4">Corey Schafer</a>
</li>
<li>
<a href="https://www.youtube.com/watch?v=wBp0Rb-ZJak">Joe Collins ( Commandline ) </a>
</li>
<li>
<a href="https://www.youtube.com/watch?v=YHFzr-akOas&list=PLS1QulWo1RIb9WVQGJ_vh-RQusbZgO_As">Programming Knowledge ( Commandline ) </a>
</li>
</ul>
</section>
<section>
<header> <u> Online Tutorials </u> </header>
<ul class="resource-links">
<li>
<a href="https://www.codecademy.com/learn/learn-git">Codecademy ( Learn Git ) </a>
</li>
<li>
<a href="https://www.tutorialspoint.com/git/">Tutorials Point </a>
</li>
<li>
<a href="https://github.com/jlord/git-it-electron/releases">Git-It</a>
</li>
<li>
<a href="https://services.github.com/on-demand/downloads/github-git-cheat-sheet/">Git Cheat Sheet</a>
</li>
</ul>
</section>
</section>
<section>
<header> <u> QUESTION </u> </header>
<img height="400" data-src="question.jpeg"/>
</section>
<section>
<section>
<header>To get in touch with me </header>
<p>Gmail: <a href="#"> zombieleetnca@gmail.com </a> </p>
<p>Twitter: <a href="https://twitter.com/VOsikwemhe"> @VOsikwemhe </a> </p>
<p>Github: <a href="https://github.com/zombieleet"> @zombieleet </a> </p>
</section>
<section>
<header> <u> THE END </u> </header>
<img height="500" data-src="version_control_all_things.jpeg"/>
</section>
</section>
</div>
</div>
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.js"></script>
<script>
// More info about config & dependencies:
// - https://github.com/hakimel/reveal.js#configuration
// - https://github.com/hakimel/reveal.js#dependencies
Reveal.initialize({
dependencies: [
{ src: 'plugin/markdown/marked.js' },
{ src: 'plugin/markdown/markdown.js' },
{ src: 'plugin/notes/notes.js', async: true },
{ src: 'plugin/highlight/highlight.js', async: true, callback: function() { hljs.initHighlightingOnLoad(); } }
]