Copyright © 2014 Splunk Inc.

Using Git and Github for
Non-Developers
Hal Rottenberg - January 2014
Agenda
Source Code Management Basics
What is Git (And why use it?)
What is Github?

Typical use cases for non-developers
T...
Expectations
Hal is not a developer and does not claim to be one
Concepts will be simplified or MAYBE EVEN WAY WRONG
You w...
Source Code Management Basics
Maintain sets of changes (revisions) to text files
Can be centralized or distributed
Key str...
What is Git?
Free software made by Linus Torvalds for Linux kernel development in
2005
Distributed SCM
No server, minimal ...
Why use it?
Team size = 1; maybe just use Box
>1 (or ever hope to have help); SCM is awesome
Git is among the easier SCM t...
What is Github?
Commercial service which provides git hosting
Social network for developers which encourages collaboration...
Typical use cases for non-developers
Splunk app development
Script repository
Change control

8
How to get started?
Download GUI client from
http://github.com (includes
CLI)
Clone an existing repo, or
add existing code...
Tutorials
Create new local repo
Clone repo from web
Commit changes

Review changes

10
What’s Next?
Branching
Pull requests
Tagging

11
Questions?

12
Upcoming SlideShare
Loading in …5
×

Using git and github for non developers

1,628 views

Published on

This was from a 1-hour lunch & learn session given Jan 2014 by myself to an audience consisting mostly of technical field personnel (titles like solution architect, pre-sales engineer, professional services engineer). The hook is that when working with deploying and maintaining complex software with many text configuration files (like Splunk), or when working in very small teams on "casual" software development or just hacking some scripts together, it's very beneficial to have a source code management tool in place. I chose git, and highlighted the sorts of features that this tool provides to those who ARE NOT developers.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,628
On SlideShare
0
From Embeds
0
Number of Embeds
13
Actions
Shares
0
Downloads
9
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Using git and github for non developers

  1. 1. Copyright © 2014 Splunk Inc. Using Git and Github for Non-Developers Hal Rottenberg - January 2014
  2. 2. Agenda Source Code Management Basics What is Git (And why use it?) What is Github? Typical use cases for non-developers Tutorials 2
  3. 3. Expectations Hal is not a developer and does not claim to be one Concepts will be simplified or MAYBE EVEN WAY WRONG You won’t care and it doesn’t matter* Please ask questions! 3
  4. 4. Source Code Management Basics Maintain sets of changes (revisions) to text files Can be centralized or distributed Key strengths: workflow, collaboration, data integrity Common terms include: – – – – – – – Working tree (folder | directory) Add / checkin / checkout / clone Commit / Commit log Diff Branch / merge Push / Pull / Sync Tag 4
  5. 5. What is Git? Free software made by Linus Torvalds for Linux kernel development in 2005 Distributed SCM No server, minimal requirements, easy to setup and use CLI and GUI clients available for all platforms Plugins exist for many text editors and IDEs 5
  6. 6. Why use it? Team size = 1; maybe just use Box >1 (or ever hope to have help); SCM is awesome Git is among the easier SCM tools to use Mature GUI clients for Mac & Windows Very well documented, rabid fanbase community Alternatives: SVN, Mercurial (hg), Perforce 6
  7. 7. What is Github? Commercial service which provides git hosting Social network for developers which encourages collaboration Free and paid options Publishes widely-used Mac and Windows GUI clients Lightweight wiki and issue tracking features 7
  8. 8. Typical use cases for non-developers Splunk app development Script repository Change control 8
  9. 9. How to get started? Download GUI client from http://github.com (includes CLI) Clone an existing repo, or add existing code to a new repo 9
  10. 10. Tutorials Create new local repo Clone repo from web Commit changes Review changes 10
  11. 11. What’s Next? Branching Pull requests Tagging 11
  12. 12. Questions? 12

×