Fully fleshed out basic github workshop

Author: AOrps

README.md

@@ -1 +1,24 @@
-# basic-github-workshop
+# basic-github-workshop
+* Inspiration for this repo from [jctf-pres](https://github.com/iloveicedgreentea/jerseyctf-presentation)
+
+## Table of Contents
+<!-- (15 minutes and 10 minutes of questions) -->
+* [Why](docs/why.md)
+* [Git & Version Control](docs/gitVC.md)
+* [Commits](docs/commits.md)
+* [Branches](docs/branches.md)
+* [Remotes](docs/remotes.md)
+* [Commands](docs/commands.md)
+* [Conclusion](docs/conclusion.md)
+
+## Purpose of this Presentation 
+
+An intro guide into Github. And the beauty of it!
+
+
+<!-- Flow:  OG -> WHY -> GITVC -> commits -> branches -> remotes -> commands -> conclusion --> 
+
+<!-- DONE: OG, WHY, GITVC, commits, branches, remotes, commands, Conclusion-->
+
+[Start Presentation](docs/why.md)
+

docs/branches.md

@@ -0,0 +1,29 @@
+# Branches
+
+![](../img/branchLolz.jpeg)
+
+
+**Branches** are ways to isolate development work without affecting other branches in the repository. 
+
+Every repository (repo) has at least 1 default branch. 
+
+_Conventionally_, branches allow:
+* Development of Features
+* Bug Fixes
+* Environment for Experimenting of new ideas, safely
+
+## Commands
+
+To create a new branch
+* `git branch <BranchName>`
+
+To switch into a different branch
+* `git checkout <BranchName>`
+
+To create and switch to branch
+* `git checkout -b <BranchName>` 
+
+
+---
+
+[next](remotes.md)

docs/commands.md

@@ -0,0 +1,45 @@
+# Commands (Git Commands)
+
+Take a look at the [***GIT Cheat Sheet***](#gcs) in the **Resources** section for a more extensive list of commands
+
+## Setup
+To add your Github Username
+* `git config --global user.name`
+
+To add your Github Email
+* `git config --global user.email`
+
+## Initialization
+
+To Initialize an existing directory as a Git repository
+* `git init`
+
+To clone a repository (Download current version from repository)
+* `git clone <url>`
+
+
+## Development 
+
+To stage your files (add to the commit)
+* `git add .`
+
+To commit changes
+* `git commit -m "Commit Message"`
+
+To push to the current remote and the current branch
+* `git push`
+
+Update repository content from the current remote and current branch
+* `git pull`
+
+* **THESE ARE BIT A FRACTION OF ALL THE POSSIBLE GIT COMMANDS, but they are are some of the most common**
+
+
+---
+
+## Resources
+<b id="gcs">[GIT Cheat Sheet](https://education.github.com/git-cheat-sheet-education.pdf)</b>
+
+---
+
+[next](conclusion.md)

docs/commits.md

@@ -0,0 +1,26 @@
+# Commits
+
+![](../img/commitsLolz.jpeg)
+## What is it?
+Simply put, **Commits** are saved changes. 
+
+## Commits Explained
+Each commit has an associated _commit message_. A **good _commit message_** is a description why a particular change was made or the changes themselves.
+
+Git assigns each commit a unique ID, called a SHA or hash, that identifies:
+* The specified changes
+* When the changes were made
+* Who created the changes
+
+## Command
+`git commit -m "<A descriptive change>"`
+
+## Funny Commit meme
+![](../img/breakProdCommit.jpg)
+> Commits that are meaningful and make the repo better are wonderful ;)
+
+* Hmm, surely there must be a way to commit to a repo without breaking anything that might be really important. 
+
+---
+
+[next](branches.md)

docs/conclusion.md

@@ -0,0 +1,23 @@
+# Conclusion
+
+Hope you are sold on Github! 
+
+
+![](../img/githubPog.jpg)
+
+Git is an incredibly powerful tool that can help you build anything that might interest you! 
+
+With Github and Git by your side, you are virtually unstoppable when it comes to **Software Development** and **Product Development**! 
+
+
+Feel free to come on and try it for yourself! Or look into the [Advanced Github Techniques](https://github.com/njitacm/advanced-github-workshop) (if you up for the challenge)
+
+> Also, highly recommend looking at github memes, sometimes very funny
+
+## Resources
+* [Why Git Sucks and you'll use it anyways](https://www.slideshare.net/CarlosTaborda/why-git-sucks-and-youll-use-it-anyways)
+    * After Slide 21, it actually has some meaning stuff that will help with understanding the fundamentals
+
+---
+
+[start over](../README.md)

docs/gitVC.md

@@ -0,0 +1,42 @@
+# Git & Version Control
+
+![](../img/vcMeme.jpg)
+
+## Decoupling the Git in Github
+
+### Github and Git are 2 different things
+
+**Git**  is  the  free  and  open  source  distributed  version  control  system  that's  responsible  for  everything  GitHub related that happens locally on your computer.
+
+**Github** is a code hosting platform for version control and collaboration. It lets you and others work together on projects from anywhere.
+
+![](../img/gitVgithub.png)
+
+---
+
+## Version Control?
+Version Control goes by many names:
+* Revision Control
+* Source Control
+* Source Code Management
+
+Version Control is a sclass of systems responsible for managing changes to any type of DATA.
+* Code
+* Documents
+* Backend Infrastructure
+* Collection of information
+* Executables / Programs
+* Anything that can be on a computer can be on Github
+
+
+> But what does it actually mean?
+* As long as you push to Github, your code is saved. 
+    * But not only your code, your entire history of your code is saved. 
+
+* You can work with your code without worrying about messing anything up
+    * Via Branching, you can your main production branch and also a feature branch so if you mess anything up you, you don't actually mess anything up
+
+
+---
+
+[next](commits.md)

docs/remotes.md

@@ -0,0 +1,26 @@
+# Remotes
+
+![](../img/gitRem.png)
+> No meme sorry
+<!-- REMOTES ARE NO JOKING MATTER lol(MEME-less) -->
+
+
+
+A remote URL is Git's fancy way of saying **"the place where your code is stored"**
+
+That URL could be your repository on Gitub, or another user's fork, or even on a completely different server. 
+
+
+## Commands
+To create remote repositories
+* `git remote add <RemoteName> <RemoteURL>`
+
+To change remote's URL
+* `git remote set-url <RemoteName> <RemoteURL> `
+
+## Resources
+* [Git remote Commands](https://git-scm.com/docs/git-remote)
+
+---
+
+[next](commands.md)

docs/why.md

@@ -0,0 +1,41 @@
+# why?
+Why not?
+
+![](../img/githubMeme.jpg)
+
+**GitHub** is a website for **developers** and **programmers** to collaboratively work on code. The primary benefit of **GitHub** is its version control system, which allows for seamless collaboration without compromising the integrity<sup>[1](#f1)</sup> of the original project. The projects on GitHub are examples of open-source software.
+
+<sup id="f1">1</sup> Some `l33t` hackers can manipulate integrity on Github. 
+
+* Check out Contributors on [SigMal](https://github.com/AOrps/SigMal)
+    * One of them seems like they don't quite fit
+
+
+## Benefits
+
+* Github as a 'Code Portfolio'
+    * Show off your technical and coding expertise
+
+* Build Software Engineering Products
+    * Lots of production Code is on Github (i.e. Linux Kernel, cpython, snort3, etc)
+
+* For those ***BEAUTY GREEN SQUARES*** that make contribution
+
+![](../img/count-mid.png)
+
+Just note there is always another person, with more commits than you!
+
+![](../img/theGuySheTellsYouNotToWorryAbout.png)
+
+
+
+* Also use it as a place for information
+    * [Red Teaming Toolkit](https://github.com/infosecn1nja/Red-Teaming-Toolkit)
+    * [Zero-to-mastery/start-here-guidelines](https://github.com/zero-to-mastery/start-here-guidelines)
+    * [SigMal](https://github.com/AOrps/SigMal)
+    * [Awesome OSCP](https://github.com/0x4D31/awesome-oscp)
+
+
+---
+
+[next](gitVC.md)