-
Notifications
You must be signed in to change notification settings - Fork 2
/
index.html
1096 lines (1078 loc) · 58 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 lang="en">
<head>
<meta charset="utf-8">
<title>GitHub for Cats!</title>
<meta name="description" content="GitHub is so easy your cat can use it!">
<meta name="author" content="Eric Steinborn">
<meta name="keywords" content="excelsior,responsive web design,new york state,its">
<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
<link rel="stylesheet" href="css/reveal.min.css">
<link rel="stylesheet" href="css/theme/beige-custom.css" id="theme">
<link rel="apple-touch-icon" href="apple-touch-icon.png">
<link rel="apple-touch-startup-image" media="(device-width: 320px)" href="img/forcats-startup.png">
<link rel="icon" href="favicon.ico">
<!-- For syntax highlighting -->
<!-- If the query includes 'print-pdf', use the PDF print sheet -->
<script>
(function() {
var printcss = '<link rel="stylesheet" href="';
if (window.location.search.match(/print-pdf/gi)) { printcss += 'css/print/pdf'; }
else if (window.location.search.match(/print-speaker/gi)) { printcss += 'css/theme/print-speaker'; }
else { printcss += 'css/print/paper'; }
printcss += '.css" type="text/css" media="print">';
console.log(printcss);
document.write(printcss);
}());
var tag = document.createElement('script');
tag.src = "https://www.youtube.com/iframe_api";
var firstScriptTag = document.getElementsByTagName('script')[0];
firstScriptTag.parentNode.insertBefore(tag, firstScriptTag);
</script>
<!--[if lt IE 9]><script src="lib/js/html5shiv.js"></script><![endif]-->
</head>
<body>
<div id="install" class="install hidden">
<h1>GitHub for Cats!</h1>
<h2>By Eric Steinborn</h2>
<div class="bottom">
<p><img src="img/forcats.jpg" width="320px" alt=""></p>
<p><a href="?overrideinstaller" class="override">Override Install message</a></p>
<p>Tap this icon and <strong>Add to Home Screen</strong></p>
<p>▼</p>
</div>
</div>
<div class="reveal" id="reveal">
<script>
if (!window.location.search.match(/overrideinstaller/gi)) {
var homescreenInstaller = function(){
if (window.navigator.userAgent.indexOf('iPhone') != -1) {
if (window.navigator.standalone != true) {
var install = document.getElementById("install"),
slideshow = document.getElementById("reveal");
install.classList.remove("hidden");
reveal.classList.add("hidden");
}
}
}();
}
// homescreenInstaller();
</script>
<!-- Any section element inside of this container is displayed as a slide -->
<div class="slides">
<section>
<h1 class="superhuge">GitHub</h1>
<h1>for Cats!</h1>
<h3>(cool, not-so-cool, all kinds of cats)</h3>
<p><a href="http://www.github.com">Sign up for GitHub before we begin:<br>www.github.com</a></p>
<aside class="notes">
<p></p>
</aside>
</section>
<section data-state="githubmusicvideo" data-background="#222222">
<iframe id="player" width="911" height="548" src="//www.youtube.com/embed/qT90jZP58jM?rel=0&iv_load_policy=3&vq=hd720" frameborder="0" allowfullscreen></iframe>
<p class="bright-text">"Better Together" Official GitHub Music Video</p>
<aside class="notes">
<p></p>
</aside>
</section>
<section data-state="kittenvideo" data-background="#222222">
<iframe id="playertwo" width="800" height="600" src="//www.youtube.com/embed/0Bmhjf0rKe8?rel=0&iv_load_policy=3&vq=hd720" frameborder="0" allowfullscreen></iframe>
<p class="bright-text">"Surprised Kitty" - 71,737,029 Views</p>
<aside class="notes">
<p></p>
</aside>
</section>
<section data-background="#F6F7F2">
<h1>GitHub for Cats!</h1>
<img src="img/forcats.png" class="no-shadow no-border" alt="">
<aside class="notes">
<p>Welcome to the wonderful world of GitHub ...for cats</p>
<p>I'm Eric Steinborn and I'll be your guide today.</p>
<p>You just watched the Official GitHub Music video, and since you're attending gitHub for cats, you also watched the most viewed cat video on the internet, Surprised Kitty.</p>
<p>My Goal today is for you to leave with a firm understanding of What GitHub is, how to use it.</p>
<p>most importantly though, why you should use it to Unlock your teams true potential</p>
<p>Let's begin with the most important question of all</p>
</aside>
</section>
<section>
<h2>Why call it "GitHub for Cats?"</h2>
<p>GitHub's mascot is a cross between an Octopus and a Cat</p>
<p><img class="no-border no-shadow" style="padding-right:10px;" src="img/original.png" height="300" alt="Octocat" title="Octocat"><img class="fragment no-border no-shadow" style="padding-right:10px;" height="300" src="img/jean-luc-picat.png" alt="Jean-Luc Picard-styled Octocat" title="Jean-Luc Picat"><img class="fragment no-border no-shadow" style="padding-right:10px;position:relative;top:6px;" height="300" src="img/ironcat.png" alt="Ironman-styled Octocat" title="Ironman Octocat"></p>
<p><a href="http://octodex.github.com/">View the Octodex</a></p>
<aside class="notes">
<p>Their mascot is a cross between an octopus and a cat — an octocat</p>
<p>Their employees have a lot of fun creating different renditions of their beloved mascot</p>
<p>Renditions such as the jean luc picat for my fellow trekkies out there</p>
<p>or how about the Iron cat, for any iron man fans out there!</p>
<p>I wanted to create a title that meant that GitHub was easy to use, So my subtitle is GitHub is so easy your Cat could use it! and after today hopefully you'll agree.</p>
<p>so now that ive answered the most important question of the day, I'll answer the second most important question.</p>
</aside>
</section>
<section>
<h2>So What is GitHub Anyway?</h2>
<p>Version control hosting for projects</p>
<p class="fragment">Featuring a robust set of collaborative tools.</p>
<aside class="notes">
<p>Version control for your projects, But that would be selling it short, as it's much more than just source control</p>
<p>It's Version Control with a robust set of collaborative and project management tools</p>
<p>They actually created a video that can explain it a million times better than I can.</p>
<p>sorry in advance about the silly alien music midway through it.</p>
</aside>
</section>
<section data-state="githubvideo" data-background="#222222">
<iframe id="playerthree" width="911" height="548" src="//www.youtube.com/embed/l_T3XEgXl14?rel=0&iv_load_policy=3&vq=hd720" frameborder="0" allowfullscreen></iframe>
<p class="bright-text">GitHub is Changing the World</p>
<aside class="notes">
<p></p>
</aside>
</section>
<section>
<h2>GitHub is the De Facto Standard</h2>
<ul>
<li>5.5 million developers</li>
<li>16.4 million hosted projects</li>
<li>Running a 99.96% uptime</li>
</ul>
<aside class="notes">
<p>gitHub is home to millions of developers hosting over 10 million projects, featuring an uptime just won't quit</p>
<p>Many job applications list GitHub knowledge as a requirement.</p>
<p>And I don't blame them, Everyone should use version control for their projects.</p>
<p>I've mentioned version control, what exactly is version control?</p>
</aside>
</section>
<section data-transition="fade">
<h1>Version Control</h1>
<p>Keep old versions of files for archival or future use.</p>
<aside class="notes">
<p>Version Control is the process of keeping old versions of files for archival or future use.</p>
<p>Did you just push a feature that broke your app? use version control to go back in time and grestore your app back to a time when it wasn't broken.</p>
<p>May have heard it called revision control, or source control</p>
<p>Lets take a short stroll back through time to see the history of version control</p>
<p>A title that would better describe what I'm about to tell you would be</p>
</aside>
</section>
<section data-transition="fade">
<h1>A brief, and incomplete history of version control.</h1>
<p class="fragment">We're in charge of updating the employee handbook...</p>
<aside class="notes">
<p>A brief, and incomplete history of version control.</p>
<p>To demonstrate this concept we'll pretend we're in charge of updating the employee handbook.</p>
</aside>
</section>
<section>
<h2>In the Beginning..</h2>
<p>Store my files in a folder on your computer (Repo)</p>
<p><img src="img/folder.jpg" alt=""></p>
<p class="fragment">Employee Handbook.doc</p>
<aside class="notes">
<p>file is stored in a folder, Otherwise known as your project repository, or repo</p>
<p>You create Employee Handbook.doc</p>
</aside>
</section>
<section>
<h1>Early Version control</h1>
<p>Employee Handbook.doc</p>
<p class="fragment">Employee Handbook_01.doc</p>
<p class="fragment">Employee Handbook_Final.doc</p>
<p class="fragment">Employee Handbook_FINAL.doc</p>
<p class="fragment">Employee Handbook_02-02-1998.doc</p>
<p class="fragment">Employee Handbook_Final_01_FINAL.doc</p>
<aside class="notes">
<p>early version control meant that you changed the name of your document each save.</p>
<p>goes on and on and on, never remembering which one is the one to go with</p>
<p>Sort by date? Well you just started working here and the person who used to maintain the file left, and you need to find out which one is the right one.</p>
<p>very confusing, untenable</p>
</aside>
</section>
<section>
<h1>There's Got to be a Better Way!</h1>
<p class="fragment"><img src="img/betterway.gif" width="500px" alt=""></p>
<aside class="notes">
<p>I have folders upon folders of projects that I used to maintain this way, and it drives me crazy.</p>
<p>Maintaining your files and projects this way is like cutting break with a wodden doorstop, Sure you'll get there eventually, but</p>
<p>there's got to be a better way!</p>
<p>So there were some better version control systems that came out, you may already be familiar with some of them, CVS, SNVN, Mercurial, but along comes this heavyweight contender...</p>
</aside>
</section>
<section>
<h1>GitHub</h1>
<p>Version control = Central repo, 1 file name full history</p>
<p>+ incredible social and project management toolkit</p>
<p><img src="img/collabocats.png" height="400px" alt=""></p>
<aside class="notes">
<p>one project folder, hosted on a server, 1 filename, with a history of every change ever made to that file.</p>
<p>git vc, but hosted on a public site featuring a ton of social features to help create some of the best projects on the internet.</p>
<p><strong>Publish them</strong> or <strong>keep them private</strong>.</p>
<p>very basic using one document, but this scales easily as we'll see soon.</p>
<p>Lets learn the basics of Version Control using GitHub</p>
</aside>
</section>
<section data-transition="fade">
<h2>Repository is on a Server</h2>
<p>Your Project is hosted</p>
<p><img src="img/repo.png" class="workflow-image" alt=""></p>
<aside class="notes">
<p>files are on a server, and you need to make a local copy of it in order to make changes.</p>
</aside>
</section>
<section data-transition="fade">
<h2>Clone</h2>
<p>Copy repo to your local machine</p>
<p><img src="img/clone.png" class="workflow-image" alt=""></p>
<aside class="notes">
<p>files are on a server, and you need to make a local copy of it in order to make changes.</p>
<p>Similar to Photocopying the master copy</p>
<p>So we need to make some changes to that file</p>
</aside>
</section>
<section data-transition="fade">
<h2>Commit</h2>
<p>Make your changes locally</p>
<p><img src="img/commit.png" class="workflow-image" alt=""></p>
<aside class="notes">
<p>Commit: A snapshot of your project in time.</p>
<p>you make changes to this photocopy, while leaving the original on the server untouched.</p>
<p>all changes thus far are local to you, they are not on the server yet</p>
<p>Once you are done, you'll want to push your changes to the server, appropriately named "push command" »</p>
</aside>
</section>
<section data-transition="fade">
<h2>Push (Sync)</h2>
<p>Apply your changes to central repo</p>
<p><img src="img/push.png" class="workflow-image" alt=""></p>
<aside class="notes">
<p>push your changes to the server</p>
<p>Your Photocopy has now become the new master copy</p>
<p>old master copy still fully intact in its old state, It's just filed away for easy access if you evry wanted to go back or view the changes( better metaphor)</p>
<p>github is social though</p>
</aside>
</section>
<section data-transition="fade">
<h2>Social!</h2>
<p>Add new developers to the mix</p>
<p><img src="img/new-challenger.png" class="workflow-image" alt=""></p>
<aside class="notes">
<p>it allows your projects to be copied to other users, (if you're not using a private system)</p>
</aside>
</section>
<section data-transition="fade">
<h2>Fork</h2>
<p>Create their own copy of your repo</p>
<p><img src="img/fork.png" class="workflow-image" alt=""></p>
<aside class="notes">
<p>Make a copy of your repo on the server and download it locallt</p>
</aside>
</section>
<section data-transition="fade">
<h2>Commit</h2>
<p>Make their changes locally</p>
<p><img src="img/fork-commit.png" class="workflow-image" alt=""></p>
<aside class="notes">
<p>Correct it , spelling errors</p>
<p>add new features</p>
<p>then they want to request that you pull in their changes into your repo</p>
</aside>
</section>
<section data-transition="fade">
<h2>Push</h2>
<p>Push their changes to their forked copies</p>
<p><img src="img/fork-push.png" class="workflow-image" alt=""></p>
<aside class="notes">
<p>Correct it , spelling errors</p>
<p>add new features</p>
<p>then they want to request that you pull in their changes into your repo</p>
</aside>
</section>
<section data-transition="fade">
<h2>Pull</h2>
<p>They request you pull their changes into your repo</p>
<p><img src="img/pull-request.png" class="workflow-image" alt=""></p>
<aside class="notes">
<p>Here are my changes, they are better because of XYZ</p>
<p>Sorry Jimmy, but that was intentionally mispelled</p>
<p>Thanks Jane, This really could benefit from the addition of a cat-focused history of the internet</p>
</aside>
</section>
<section data-transition="fade">
<h2>Push</h2>
<p>Push their changes to your repo</p>
<p><img src="img/pull-request-push.png" class="workflow-image" alt=""></p>
<aside class="notes">
<p>You decide what stays and what goes.</p>
<p>But these people don;t have to be people you already know, they can be anyone, Github is global</p>
</aside>
</section>
<section>
<h2>GitHub is Global</h2>
<p><img src="img/benevocats.png" height="550px" alt=""></p>
<aside class="notes">
<p>My plugin was updated by someone in the UK</p>
<p>Before we get into how to use GitHub, I'd like to tell you about one of the first times ITS utilized GitHub. and the results that effort produced.</p>
</aside>
</section>
<section>
<h1>Responsive Web Design (RWD) SWAT Team</h1>
<aside class="notes">
<p>Back in March of 2013, CTO's office heard about this thing called responsive web design.</p>
<p>The web was aflutter about it, and the CTO's office wanted to learn more.</p>
<p>So it put together a group of 10 developers to perform some R&D on Responsive Web Design</p>
</aside>
</section>
<section>
<h2>Stats</h2>
<ul>
<li>10 people, 3 weeks, full time</li>
<li class="fragment">1700 commits</li>
<li class="fragment">899 issues resolved</li>
</ul>
<aside class="notes">
<p>a years worth of work in 3 weeks. amazing experience.</p>
<p>1700 commits</p>
<p>899 issues addressed</p>
<p>GitHub facilitated the collaboration we needed to produce some deliverables.</p>
</aside>
</section>
<section>
<h2>RWD Sprint Deliverables</h2>
<ul>
<li class="fragment">Alpha version of a RWD framework (<a href="https://github.com/nys-its/excelsior">Excelsior</a>)</li>
<li class="fragment">"Getting Started" website created (<a href="http://nys-its.github.com/go-responsive/">GoResponsive</a>)</li>
</ul>
<aside class="notes">
<p>build the foundation for a framework</p>
<p>getting started guide featuring 16 rwd demos showing off techniques to build responsive websites.</p>
<p>All left with advanced knowledge of RWD and how we can use it at the state</p>
<p>A resource that all of NYS, nay the world can use to get started with RWD</p>
<p>So we know what version control is, and a little bit about how github is different, so lets dig into GitHub now.</p>
</aside>
</section>
<section>
<h1>Set up GitHub</h1>
<ul>
<li>Sign up for a GitHub account</li>
<li>Install GitHub for Windows</li>
<li>Create first repo</li>
</ul>
<aside class="notes">
<p></p>
</aside>
</section>
<section>
<h2>Create GitHub Account</h2>
<p><a href="http://www.github.com">www.github.com - Sign up link</a></p>
<p><img src="img/screen01.png" alt="Sign up page"></p>
<aside class="notes">
<p>The excitement of being the first person to sign up in your agency.</p>
</aside>
</section>
<section>
<h2>Download GitHub for Windows</h2>
<p><a href="http://windows.github.com">windows.github.com - GitHub for Windows</a></p>
<p><img src="img/screen02.png" alt="Download page"></p>
<aside class="notes">
<p>Here is the download page for downloading the client, You'll click the big button at the top of the page to download it.</p>
</aside>
</section>
<section>
<h2>Install GitHub for Windows</h2>
<p><img src="img/install.png" alt="Install screen"></p>
<aside class="notes">
<p>Here is the install screen. after the installation you'll be prompted with a screen to add your credentials that you created on github.com</p>
</aside>
</section>
<section>
<h2>First Run</h2>
<p><img src="img/first-run.png" alt="First Run, enter username password"></p>
<aside class="notes">
<p>enter in your credentials</p>
<p>hit run, and you're off. The program is now fully installed.</p>
<p>Let's create your first repo on GitHub</p>
</aside>
</section>
<section data-transition="fade">
<h1>Create Your First Repo</h1>
<p><img src="img/dragndrop.gif" alt="drag-drop folder into project"></p>
<aside class="notes">
<p>Creating a repo is really simple using the GitHub for windows client.</p>
<p>it's literally a drag and drop operation to turn any existing project into a GitHub repo.</p>
<p>We'll create a new repo from a project we've been working on about Kittens</p>
<p>After you drag the folder into GHW, you'll get prompted to fill in some information about it »</p>
<p>We'll come up with a good name for our repo, we'll call it, Kittens.</p>
<p>Here you can decide if you want to push it to gitHub immediately or not, I'll say no this time, and show you how to do it in the GUI.</p>
<p>It's that simple to create a new project on GitHub.</p>
</aside>
</section>
<section data-transition="fade">
<h2>GUI Home Screen</h2>
<p><img src="img/screen06.png" alt=""></p>
<aside class="notes">
<p>so now we're left at the home screen lets take a look around.</p>
</aside>
</section>
<section data-transition="fade">
<h2>GitHub Repo List</h2>
<p><img src="img/screen05.png" alt=""></p>
<aside class="notes">
<p>Clicking on your username under the "GitHub" category will show you any repo that you haven't cloned yet</p>
<p>The list on the right is populated with any repositories that you have created or forked on GitHub</p>
<p>double click a repo in this list to clone that repo onto your local machine.</p>
<p>Once a repo has been cloned locally it will be located here and under the Local category</p>
</aside>
</section>
<section data-transition="fade">
<h2>Local Repo List</h2>
<p><img src="img/screen06.png" alt=""></p>
<aside class="notes">
<p>When you select "repositories" under the "local" category, the right side of the screen displays a list of any local repos.</p>
<p>To be a local repo, you must have either not synced it to GitHub yet, like our kittens repo, or you have cloned it to your local computer from GitHub.</p>
<p>Let's take a look at our Kittens repo now. WE'll double click on the Kittens repo and we'll be brought to the repo screen.</p>
</aside>
</section>
<section data-transition="fade">
<h2>Committing</h2>
<p><img src="img/screen07.png" alt=""></p>
<aside class="notes">
<p>So we created this Kittens repo, but we havent pushed it to GitHub yet. Let's do that now.</p>
<p>On the repo screen you'll see a box on the top left that tells us that we havent committed the new repo to the server yet.</p>
<p>This commit box will also be present any time you make any changes to your project</p>
<p>We'll need to provide a short message indicating the changes we made.</p>
<p>Since this is the first time we're pushing this to GitHub I prefer to just make that message "Initial Commit" and click the commit button at the bottom of that box.</p>
<p>Let's push this baby to GitHub now!</p>
</aside>
</section>
<section data-transition="fade">
<h2>Push to GitHub</h2>
<p><img src="img/screen09.png" alt=""></p>
<aside class="notes">
<p>The top right of the window features the button that makes all the GitHub magic happen.</p>
<p>Press that "Push to GitHub" button and you'll send all your local commits to GitHub</p>
</aside>
</section>
<section data-transition="fade">
<h2>Commit List</h2>
<p><img src="img/screen08.png" alt=""></p>
<aside class="notes">
<p>So we made our commit, and we pushed to GitHub, notice now that your commit gets added to the top of the commit list.</p>
<p>We only see one for now, but each additional commit would get stacked on top of our initial commit</p>
<p>this list allows you to click on different commits throughout the project's lifespan and see all of the changes that commit featured.</p>
</aside>
</section>
<section data-transition="fade">
<h2>Differences List (Diff)</h2>
<pre class="old-code">1.| <h1>Hello, World!</h1></pre>
<pre class="new-code fragment">1.| <h1>Hey There, World!</h1></pre>
<aside class="notes">
<p>That list will show you a line by line detailed list of changes associated with that commit</p>
<p>That is called the The differences list or DIFF list</p>
<p>Original lines of text will have a red background</p>
<p>below it you'll see a line of text with a green background detailing the new line</p>
<p>this is shows line by line for any changes</p>
</aside>
</section>
<section data-transition="fade">
<h2>Push (Sync)</h2>
<p><img src="img/screen10.png" alt=""></p>
<aside class="notes">
<p>Quick note here.</p>
<p>After you push the repo to GitHub, that push button will change to a Sync button</p>
<p>you'll see a small icon next to the sync button when you have changes that need to be synced to teh server</p>
<p>And that small number icon will disappear when you have no more changes to push to GitHub.</p>
</aside>
</section>
<section>
<h2>Can You Commit?</h2>
<p><img src="img/typing.gif" alt=""></p>
<aside class="notes">
<p>So there you have it. That's how you create a new GitHub repo, and an in-depth overview of the GitHub for Windows GUI</p>
<p>As like many things with computers, Hands-on experience is key.</p>
<p>we had a lab before the presentation when many of you already signed up for GitHub, after the presentation, we'd like to offer you a chance to make your first commit using our lab.</p>
<p>Speaking of hands on Experience, I'd like to tell you another story of how NYS collaborated using GitHub</p>
</aside>
</section>
<section>
<h1>DMV SWAT Team</h1>
<aside class="notes">
<p>DMV was developing their Registration Renewal application.</p>
<p>This was a public site, so of course they they wanted it to be mobile friendly so everyone could use it.</p>
<p>the best way to make a public site mobile friendly is to develop it using RWD</p>
<p>They were really pressed for developers so they asked the CTO's office for help.</p>
<p>we mobilized another swat team to help them out.</p>
</aside>
</section>
<section>
<h2>Stats</h2>
<ul>
<li class="fragment">8 people, 2 days, 1 week part time</li>
<li class="fragment">256 commits</li>
<li class="fragment">278 issues resolved</li>
</ul>
<aside class="notes">
<p>8 people, 2 days full time co-located, followed by a week of part time remote located</p>
</aside>
</section>
<section>
<h2>DMV Sprint Deliverables</h2>
<ul>
<li>Fully responsive Registration Renewal Application</li>
<li class="fragment">RWD framework for future apps</li>
<li class="fragment">Collaboration effort which NYS has never seen before</li>
</ul>
<aside class="notes">
<p>Created NYS's first responsive transactional application.</p>
<p>More importantly we created a re-usable template for future DMV apps</p>
<p>The RWD swat team proved that we could get a group together to research a topic</p>
<p>The DMV SWAT team proved that we could all do it remotely.</p>
</aside>
</section>
<section>
<h2>Remote Collaboration</h2>
<p>Not just 8 people..</p>
<p class="fragment">But 4 different Agencies</p>
<p class="fragment">..in 4 different buildings</p>
<p class="fragment">..working as time alowed.</p>
<aside class="notes">
<p>8 people.. 4 Agencies 4 buildings ..all working on the same project, as time allowed. That 20% time wasnt the same for everyone. We had the flexibility to chime in at any time 24/7, when our schedules allowed, and the team was kept in the loop.</p>
<p>This was what ITS has been talking about. This was true cross-cluster collaboration</p>
<p>More importantly though, I think it broke the mold of what NYS previously considered collaboration.</p>
<p>I want to let you in on a secret. this collaboration would have never occurred if it weren't for a single directective.</p>
<p>Use GitHub.com</p>
</aside>
</section>
<section>
<h1>Use GitHub.com</h1>
<img src="img/labtocat.png" height="550px" alt="">
<aside class="notes">
<p>Without GitHub.com, we just have version control.</p>
<p>Github.com uniquely enabled us to do this remote collaboration with ease.</p>
<p>I'd like to tell why.</p>
</aside>
</section>
<section>
<h2>News Feed</h2>
<p><img src="img/screen11.png" alt=""></p>
<aside class="notes">
<p>First thing you see when you log into github.com is your news feed.</p>
<p>You see activity of the people, repos and issues that you are following</p>
<p>Think of it like a facebook feed, but instead of seeing pictures of half eaten lunches, and your friends latest candy crush scores</p>
<p>you'll see interesting issues and activitiy from professionals and projects you are following.</p>
<p>There is also a search box at the top of the screne to search the site.</p>
<p>Each GitHub user has their own user page. For demonstration purposes let's type in my username here</p>
</aside>
</section>
<section data-transition="fade">
<h2>User Page</h2>
<p><img src="img/screen14.png" alt=""></p>
<aside class="notes">
<p>You can see an overview of any users GitHub activity on their page</p>
</aside>
</section>
<section data-transition="fade">
<h2>User Page</h2>
<p><img src="img/screen14-01.png" alt=""></p>
<aside class="notes">
<p>Theres a follow a user to see what they do in the future as well.</p>
</aside>
</section>
<section data-transition="fade">
<h2>User Page</h2>
<p><img src="img/screen14-02.png" alt=""></p>
<aside class="notes">
<p>you'll see a list of all of their repos as well</p>
</aside>
</section>
<section data-transition="fade">
<h2>User Page</h2>
<p><img src="img/screen14-03.png" alt=""></p>
<aside class="notes">
<p>and any they have contributed to</p>
</aside>
</section>
<section data-transition="fade">
<h2>User Page</h2>
<p><img src="img/screen14-04.png" alt=""></p>
<aside class="notes">
<p>and a cute little chart of contributions over time</p>
<p>lets click my jquery plugin to see what a repo page looks like</p>
</aside>
</section>
<section data-transition="fade">
<h2>Repo Page</h2>
<p><img src="img/screen15.png" alt=""></p>
<aside class="notes">
<p>Every GitHub repo has its own page on the site</p>
</aside>
</section>
<section data-transition="fade">
<h2>Repo Page</h2>
<p><img src="img/screen15-01.png" alt=""></p>
<aside class="notes">
<p>at the top of every repo page you'll see a short description of that repo if the author created one.</p>
</aside>
</section>
<section data-transition="fade">
<h2>Repo Page</h2>
<p><img src="img/screen15-02.png" alt=""></p>
<aside class="notes">
<p>below that you'll see a general activity report of that repo</p>
</aside>
</section>
<section data-transition="fade">
<h2>Repo Page</h2>
<p><img src="img/screen15-03.png" alt=""></p>
<aside class="notes">
<p>below that you'll see all the files associated with it.</p>
</aside>
</section>
<section data-transition="fade">
<h2>Repo Page</h2>
<p><img src="img/screen15-04.png" alt=""></p>
<aside class="notes">
<p>these tabs on teh right take you to some cool features, I'll discuss Issues and Pulse later</p>
<p>You'll notice a couple of buttons on this page as well.</p>
</aside>
</section>
<section>
<h2>Clone & Download</h2>
<p><img src="img/screen16.jpg" alt=""></p>
<aside class="notes">
<p>on the right side of the screen you'll see the clone and download buttons.</p>
<p>clicking the clone in desktop button will actually bring up the GUI client and clone the repo onto your local machine.</p>
<p>clicking the download button will download a zip file of the entire repo's content</p>
</aside>
</section>
<section>
<h2>Watching & Starring Repos</h2>
<p><img src="img/screen17.jpg" alt=""></p>
<aside class="notes">
<p>if you watch a repo, any changes that happen on it will show up in your news feed</p>
<p>starring a repo is like favoriting it, and you'll have a list of all your starred repos in one place.</p>
<p>Sometimes though, you want to actually edit the code yourself. Thats where forking comes into play.</p>
</aside>
</section>
<section>
<h1>Forking</h1>
<p>It's a good thing!</p>
<p><img src="img/forking.gif" width="700px" alt=""></p>
<aside class="notes">
<p>Creating a personal copy of someone elses repo.</p>
<p>GH is social. All code on GitHub is available at your fingertips</p>
<p>You can do whatever you want with that code that their license allows you to.</p>
<p>Let's fork this repo quickly to show you how its done</p>
</aside>
</section>
<section>
<h2>Fork</h2>
<p><img src="img/fork.jpg" alt=""></p>
<p class="fragment"><img src="img/hardcore-forking.gif" alt=""></p>
<aside class="notes">
<p>When you click fork, you'll get a cute little gif of that repo getting photocopied</p>
<p>behind the scenes GitHub is creating you a personal copy of this repo and it's... available immediately</p>
</aside>
</section>
<section>
<h2>Available Immediately</h2>
<ul>
<li class="fragment">Use it on your projects</li>
<li class="fragment">Modify it</li>
<li class="fragment">Fix a bug</li>
<li class="fragment">Send back changes to original repo</li>
</ul>
<aside class="notes">
<p>Use it on your projects</p>
<p>Modify it</p>
<p>Fix a bug</p>
<p>Send back changes to original repo</p>
<p>work together to create an even better project</p>
<p>I'm asking you to take a giant leap here from traditional thinking. I'm asking you to make your code publically available, to share it and accept help and criticism from others. It can only make a project better in the long run.</p>
<p>speaking of working together, teams love github</p>
</aside>
</section>
<section>
<h1>Teams Love GitHub!</h1>
<p><img src="img/socialite.png" alt=""></p>
<aside class="notes">
<p>Having worked on three teams that used GitHub for collaboration, I have yet to meet someone who has said they didnt like github.</p>
<p>It brings teams together, and gets you motivated</p>
<p>It's great for the tiniest one-off projects all the way to huge scale archetectures..</p>
</aside>
</section>
<section>
<h2>Large Projects? No Problem</h2>
<ul>
<li class="fragment">Multiple people can edit the same file simultaneously</li>
<li class="fragment">Offline editing, commit when ready</li>
<li class="fragment">Fast workflow of your choice</li>
<li class="fragment">Long distance collaboration</li>
</ul>
<aside class="notes">
<p>large scale projects are easy to manage using GitHub.</p>
<p>be careful when editing the same line of a file</p>
<p>many VCs require you to be online to commit your changes</p>
<p>keep your changes local until you are ready to publish them</p>
<p>You aren't restricted to a specific workflow</p>
<p>and as I mentioned before, you dont even need to be in the same country to collaborate with your team.</p>
<p>on top of this, you also get a robust project management suite</p>
</aside>
</section>
<section>
<h2>Project Management Suite</h2>
<ul>
<li class="fragment">Wiki</li>
<li class="fragment">Issue tracker</li>
<li class="fragment">Code review</li>
<li class="fragment">Project dashboard</li>
</ul>
<aside class="notes">
<p>Breeds collaboration</p>
<p>Build a wiki right into your project</p>
<p>Dynamic issue tracking system.</p>
<p>Github has code review built in. with the proper workflow you can verify each line of new code to make sure it adheres yto your standards</p>
<p>Deny the request, request they make changes to conform to the standard</p>
<p>Project dashboard called "Pulse" will give you an overview of the repository as a whole, we'll talk about Issues and Pulse later.</p>
<p></p>
</aside>
</section>
<section data-transition="fade">
<h1>Issue Tracker</h1>
<p><img src="img/screen22.png" alt=""></p>
<aside class="notes">
<p>You are going to use the issue tracker to help you do a few key things..</p>
</aside>
</section>
<section data-transition="fade">
<h2>Track Bugs</h2>
<p><img src="img/screen19.png" alt=""></p>
<aside class="notes">
<p>Track Bugs in your project</p>
<p>Navigation doesnt pop up when clicked</p>
</aside>
</section>
<section data-transition="fade">
<h2>Make Feature Requests</h2>
<p><img src="img/screen20.png" alt=""></p>
<aside class="notes">
<p>Request new feature on the site.</p>
<p>Header font should be Comic Sans</p>
</aside>
</section>
<section data-transition="fade">
<h2>Ask Questions, Get Notifications</h2>
<p><img src="img/screen21.png" alt=""></p>
<aside class="notes">
<p>Ask questions, and notify your project team members</p>
<p>Will you all be available for thursdays meeting?</p>
<p>all appropriate users will be notified when issues demanding their participation of knowledge are updated or initiaited.</p>
</aside>
</section>
<section data-transition="fade">
<h2>Assign to Users</h2>
<p><img src="img/screen23.jpg" alt=""></p>
<aside class="notes">
<p>Assign someone, or yourself to fix the navigation</p>
</aside>
</section>
<section data-transition="fade">
<h2>Group in Milestones</h2>
<p><img src="img/screen25.jpg" alt=""></p>
<aside class="notes">
<p>group issues with common timelines or requirements into milestones.</p>
<p>Two issues are assigned to the beta test milestone, one before we roll out.</p>
<p>GitHub provides you a dashboard where you can view all of these at a glance.</p>
</aside>
</section>
<section>
<h1>Pulse</h1>
<p><img src="img/screen26.png" alt=""></p>
<aside class="notes">
<p>The pulse screen features all of your repos activity at a glance.</p>
</aside>
</section>
<section data-transition="fade">
<h2>Pull requests over Time</h2>
<p><img src="img/screen27.jpg" alt=""></p>
<aside class="notes">
<p>how many times have there been changes made to your project</p>
</aside>
</section>
<section data-transition="fade">
<h2>Status of Issues</h2>
<p><img src="img/screen28.jpg" alt=""></p>
<aside class="notes">
<p>You can see the status of every issue associated with your repo.</p>
<p>Which issues are open, which are recently closed</p>
<p>Throw out your giant spreadsheets filled with questions and project plans</p>
<p>utilize issues and milestones to keep track of your projects</p>
</aside>
</section>
<section data-transition="fade">
<h2>Individual Contributions</h2>
<p><img src="img/screen29.jpg" alt=""></p>
<aside class="notes">
<p>You can see who has been active, and who isn't</p>
<p>With that knowledge you can see if maybe someone needs help setting up gitHub properly</p>
<p>Or maybe someone just isnt understanding the new framework you've decided to use and needs to sit down with one of your developers and do some pair programming.</p>
<p>Lets support our team members appropriately</p>
<p>Combined individual performance = your teams overall performance</p>
</aside>
</section>
<section data-state="logoScroll">
<h2>Speaking of Contributions...</h2>
<p class="grayscale"><img src="img/google-logo.png" width="300px" alt=""> <img src="img/jquery-logo.png" width="300px" alt=""> <img src="img/android-logo.png" height="125px" alt=""><br>
<img src="img/twitter-logo.png" height="175px" alt=""> <img src="img/adobe-logo.png" height="175px" alt=""> <img src="img/linux-logo.png" alt=""> <img src="img/facebook-logo.png" height="175px" alt=""><br>
<img src="img/reddit-logo.png" width="300px" height="auto" alt=""> <img src="img/mozilla-logo.png" width="250px" height="auto" alt=""></p>
<aside class="notes">
<p>the projects that these companies have hosted on GitHub are benefiting from the work of thousands of people.</p>
<p>Using this new social coding paradigm in some form or fashion</p>
<p>look at the number people subscribed to these projects</p>
<p>its not just twitter bootstrap, its twitter plus a few thousand random coders around the world</p>
</aside>
</section>
<section>
<h2>That's Just the Beginning!</h2>
<img src="img/codercat.png" height="600px" alt="">
<aside class="notes">
<p>Thats just the beginning, I pulled a lot of content out of this presentation that I felt was too advanced for a large primarily non-hands-on group.</p>
<p>If you want to learn more about GitHub and some more advanced techniques.</p>
<p>I'm a video gamer...</p>
</aside>
</section>
<section>
<h1 class="superhuge fragment" data-fragment-index="1">LEVEL UP!</h1>
<p style="height:450px;"><img src="img/original.png" style="position:absolute; left:30%; margin-top:25px;" class="fragment fade-out" data-fragment-index="1" height="450px">
<img src="img/linktocat.png" style="position:absolute; left:30%; margin-top:0" class="fragment" data-fragment-index="1" height="450px"></p>
<aside class="notes">
<p>I love games. In the gaming world, when you get enough experience, you level up</p>
<p>Just from being here today you've already levelled up, congrats!</p>
<p>You can leave here today and tell everyone you know that you are a Level 2 GitHubber</p>
<p>if you'd like to level up even more...</p>
</aside>
</section>
<section>
<h2>Level Up With These Techniques</h2>
<ul>
<li><a href="https://help.github.com/articles/using-pull-requests">Pull Requests</a></li>
<li class="fragment"><a href="https://www.atlassian.com/git/workflows">Branching Workflows</a></li>
<li class="fragment"><a href="http://pages.github.com/">GitHub Pages</a>
<ul><li>(<a href="http://esteinborn.github.io/github-for-cats">esteinborn.github.io/github-for-cats</a>)</li></ul>
</li>
<li class="fragment"><a href="http://www.gitguys.com/topics/merging-with-a-conflict-conflicts-andresolutions/">Merge Conflicts</a></li>
</ul>
<aside class="notes">
<p>These are the next things you need to know once you get the basics down pat.</p>
<p>Pull requests are how you request your changes be pulled into another project of branch</p>
<p>branches are how I do my workflow, but understanding them is a bit more advanced than I wanted to get into today.</p>
<p>GH pages is a free web hosting platform for your projects built right into github</p>
<p>and merge conflicts. When dealing with any version control system, you'll encounter merge conflicts sometimes. they suck, but there is always a way to resolve them.</p>
</aside>
</section>
<section>
<h2>Great Resources</h2>
<ul style="float:left;">
<li><a href="http://thkoch2001.github.io/whygitisbetter">Why is Git better?</a></li>
<li><a href="http://git-scm.com/about">Awesome features of Git</a></li>
<li><a href="http://try.github.io">Trygit (Command Line)</a></li>
<li><a href="http://git-scm.com/book">ProGit Book</a></li>
</ul>
<img src="img/Professortocat_v2.png" height="500px" alt="">
<aside class="notes">
<p>Here are some great resources on getting even deeper into GitHub, give these links a try</p>
<p>yammer, irc, email, forum meetings etc.</p>
</aside>
</section>
<section>
<h1 class="superhuge">Start Today!</h1>
<h2>Thank You</h2>
<aside class="notes">
<p>Big thanks for the Forum for letting me give this presentaiton on a topic that is near and dear to my heart.</p>
<p>I think GitHub is unbelievablely awesome.</p>
<p>If you are feeling a bit overwhelmed with the possibilities of GitHub and don't know whereto start</p>
<p>don't forget the lab at the end of the presentation to help you make your first github commit.</p>
<p>And trust me, it gets easier as time goes by. It may look like a lot now but when you jump right in, you'll get the hang of it quickly.</p>
<p>Let's start today to get GitHub working for you!</p>
</aside>
</section>
<section>
<h1>Eric Steinborn</h1>
<h3>ITS Public Safety Cluster</h3>
<p><a href="mailto:[email protected]">[email protected]</a></p>
<br>
<p><a href="http://esteinborn.github.io/github-for-cats">View this presentation online:<br>
esteinborn.github.io/github-for-cats</a></p>
<p><small><a href="http://esteinborn.github.io/github-for-cats?print-pdf">Print this presentation</a></small></p>
</section>
<section>
<h1>Questions</h1>
<img src="img/octoliberty.png" height="550px" alt="">
<aside class="notes">
<p>Questions: Please try to allow time for people to ask basic questions first, if we get through the basic questions, and you haev more more advanced ones we can hit them after. I don;t want to be any more confusing than I already have. If I cant get to your question here today, feel free to email me, or ask on yammer in the revision control group. I alwas try to make myself available for things that I think are awesome.</p>
</aside>
</section>
<section>
<h5>Can you incorporate pull requests piece by piece without pulling in the whole request?</h5>
<p>You would deny te pull request, commenting on the code that you don;t want to include in the repo, and have the person re-submit their request before pulling it in.</p>
</section>
<section>
<h5>What about deployment? How do you test, approve, deploy final version? How do you keep track of that? How do you launch project for production?</h5>
<p>Use branching workflows for testing, approval and deploying. There are also automated tools, such as Travis, that reads through testing scripts, etc. Investigate travis, google “github deployment models”</p>
</section>
<section>
<h5>Examples of other types of collaboration, besides code repositories? Are there more than just code projects on github?</h5>
<p>Yes, there are GIS repositories, docs. There is only limited support for binary files such as .doc, .pdf.</p>
</section>
<section>
<h5>Can you go back after you’ve committed and pushed?</h5>
<p>Yes, windows client has a “rollback” commit button you can click, which rolls back that commit and allows you to change it. It can go back to any previous commits.</p>
</section>
<section>
<h5>How does github manage enhancements?</h5>
<p>They develop github.com on github.com. Development team announces new features on their blog posts. Though you may want to do a search on that if you are interested in learning more about it.</p>
</section>
<section>
<h5>Private repositories require subscription? Does ITS have a private repository account?</h5>
<p>Yes private repos require a subscription. ITS does have a private subscription for the organization for use with officially sanctioned ITS projects. Current ITS stance on an ITS-wide implementation is" “we’re working on it.”</p>
</section>
<section>
<h5>How easy to migrate from SVN to github?</h5>
<p>Copy your svn folder into github and now you have a github repository. GitHub is very good at working with SVN projects</p>
</section>
<section>
<h5>Cyber security and access control. How do you keep those private codes private on github? How do you host security related codel on github?</h5>
<p>Don’t put those on github. Just keep them locally.</p>
</section>
<section>
<h5>Is that also true of the zip download?</h5>
<p>Yes, because zip download only includes what’s on the github repository.</p>
</section>
<section>
<h5>How does github manage 2 conflicting pushes, i.e., changes to same line of code? and how does it handle changes to the same file, but not hte same line?</h5>
<p>Github alerts to conflicts which you have to resolve. such as when two people are editing the same line of code. But if there are no conflicts, they just get merged together.</p>
</section>
<section>
<h5>Typical security is based on roles/permissions within teams? How does github do it?</h5>
<p>Not sure if github permission system is robust down to level of files/folders. It can be assigned by user. You can use branching and a Branch master user who cna accept and deny any changes made to projects that shouldn't be changed.</p>
</section>
<section>
<h5>How many people can merge pushes into master on remote?</h5>
<p>You can decide how many people have this access through the GitHub permissions system. This can be managed thru branching as well. So person responsible handles those changes.</p>
</section>
<section>
<h5>Can you close old projects so no further changes occur?</h5>
<p>Yes, by locking out anyone else from making changes to that code, i.e., only one person can make changes to final official version. But Eric recommends not doing that, instead recommend people make changes in their branch and then decide if you want to pull them in.</p>
</section>
<section>
<h5>Can you delete repositories?</h5>
<p>Yes, it deletes your original repository, but not any forks.</p>
</section>
<section>
<h5>What about vendor specific spreadsheets? How does that fit in with github.</h5>
<p>Excel are binary files and GitHub is not currently set up to handle them easily. Eric wouldnt recommend using GitHub is you are only using binary files.</p>
</section>
<section>
<h5>If you have a group doing front-end and another using back-end. Would you see this as managing front-end development? What’s best practice? Also what about integration with testing tools?</h5>
<p>Use a brancing methodology to manage different environments, i.e., development, testing, master. Do your syncs between the different branches on the different levels. For testing you can use travis testing tools.</p>
</section>
<section>
<h5>What about multiple deployments such as slightly different versions for internal vs. external users?</h5>
<p>With a proper configuration you can configure any repository to do anything. With Travis, you can write a script to put this folder on this server, this folder on this server, and this folder on both servers -- with all the credentials, etc. needed.</p>
</section>
<section>
<h5>What about using github to find code?</h5>
<p>Eric recommends just googling, often github will show up. The github search isn’t necessarily good for topic searching.</p>
</section>
<section>
<h5>Are there strategies to attract contributors to your repository?</h5>
<p>Put it in a footer to say “developed on github” Advertise that you’re using “XYZ on github”</p>
</section>
<section>
<h5>Has github made you a better coder?</h5>
<p>Yes, because of the social aspects where people improve on what you’ve done. Also, the public nature makes you conscious of what you’re doing. And just the structure and processes involved.</p>
</section>
<section>
<h5>Should you have one github account or multiple github accounts?</h5>
<p>Eric recommends one github account and create multiple projects within that. Eric recommends using Github for Windows as opposed to command line for beginners. You can have multiple organizations associated with your one user account</p>
</section>