[
  {
    "path": "MyReadme.md",
    "content": "#Lets start markdown\n\nI just now heard about markdown\n\nAlso have an understanding of git but github has me confused\n"
  },
  {
    "path": "NewReadme.md",
    "content": "#Hello there!\n"
  },
  {
    "path": "README.md",
    "content": "### :octocat: Git Your Practice On!\n\n* 19 Git Tips for Everyday use [http://www.alexkras.com/19-git-tips-for-everyday-use](http://www.alexkras.com/19-git-tips-for-everyday-use)\n* Git Hot Tips by Wes Bos [https://wesbos.com/git-hot-tips/](https://wesbos.com/git-hot-tips/)\n* Git Reference [https://help.github.com/categories/github-pages-basics/](https://help.github.com/categories/github-pages-basics/)\n* Pro Git Online Book [http://git-scm.com/book](http://git-scm.com/book)\n* Git Ready [http://gitready.com](http://gitready.com)\n* Quick Command Practice [http://try.github.com](http://try.github.com)\n* Git Real [http://www.codeschool.com/courses/git-real](http://www.codeschool.com/courses/git-real)\n* How to GitHub: Fork, Branch, Track, Squash and Pull Request [http://gun.io/blog/how-to-github-fork-branch-and-pull-request](http://gun.io/blog/how-to-github-fork-branch-and-pull-request)\n* Learn Git Online [http://learn.github.com/p/intro.html](http://learn.github.com/p/intro.html)\n* Teach Github [https://github.com/github/teach.github.com](https://github.com/github/teach.github.com)\n* Git: The Simple Guide [http://rogerdudler.github.com/git-guide](http://rogerdudler.github.com/git-guide)\n* Git Immersion [http://gitimmersion.com](http://gitimmersion.com)\n* Git Branching [http://pcottle.github.io/learnGitBranching/](http://pcottle.github.io/learnGitBranching/)\n* Git Cheat Sheet [https://www.atlassian.com/git/tutorials/atlassian-git-cheatsheet](https://www.atlassian.com/git/tutorials/atlassian-git-cheatsheet)\n\n\nWelcome to my practice git repository where you can eff up as much as you'd like plus work with a real, living, breathing person on the other side.\nHere we learn all things git. Feel free to send me Pull Requests just to discover what it's like when a Repo Master asks you\n\n<blockquote>\n\"Can you squash your commits for us\"\n</blockquote>\n\nand you're all like...\n\n<blockquote>\n\"How the hell do I do that?\"\n</blockquote>\n\nThis is where we make those mistakes ... so don't be scared :)\n\n### Instructions\n\nFork this repo and send me a Pull Request with anything from Grandma Peggy's Crumbled Oatmeal Cookie Recipe to your favorite Sublime Text 2 preferences.\nIt's all good yo! Learning is the prize in this game.\n\n#### Typical & Highly Useful Git Commands\n\n```bash\ngit clone git@github.com:<user_name>/the-repo-you-are-cloning.git\n```\nClones your remote origin repo locally\n\n```bash\ngit fetch upstream\n```\nPulls in the remote changes not present in your local repo. Downloads objects and references from another repository.\n\n```bash\ngit merge upstream/master\n```\nMerges any changes fetched into your working files\n\n```bash\ngit add <file>\n```\nStart tracking new files and also stage changes to already tracked files\n\n``git status`` & ``git diff``\n* Tells us what files and assets have been modified and staged\n\n```bash\ngit status -s\n```\nThis will display what files have been removed, changed or modified. \n\n* (M)  - modified\n* (A)  - added\n* (AM) - file has not been altered since it was last added\n\n```bash\ngit commit -m 'the message goes here for the commit'\n```\nRecords a snapshot of the project into your history at the time of your commit.\n\n```bash\ngit add '*.<file_extension>'\n```\nThis command adds all file types with the same extension, especially from different directories. Without quotes the command will only execute within the same directory it's been called from.\n\n```bash\ngit rm --cached <file>\n```\nUnstages a file from the working tree (i.e. stops tracking the file).\n\n```bash\ngit log\n```\nRemembers all the changes we've committed so far, in the order we committed them.\n\n```bash\ngit log --summary\n```\nSee where new files were added for the first time or where files were deleted.\n\n```bash\ngit remote add origin git@github.com:<user_name>/<repo_name>.git\n```\nCreates a brand new remote repository.\n\n```bash\ngit remote -v\n```\nShow a list of the current remote repositories\n\n```bash\ngit reset <file>\n```\nRemoves the desired file from staging area.\n\n```bash\ngit branch -r\n```\nList all the remote branches currently tracked\n\n```bash\ngit remote prune origin\n```\nDeletes branch locally if it has been removed remotely. Helps to remove stale references.\n\n```bash\ngit checkout -- <target>\n```\nChanges the desired target back to the state of the last commit. A target can be a file or a directory (for example).\n\n```bash\ngit rebase\n```\nRebase allows you to [easily change a series of commits, reordering, editing, or squashing commits together into a single commit](https://help.github.com/articles/interactive-rebase).\n\nBe warned: it's considered bad practice to rebase commits which you have already pushed to a remote repo. Doing so may invoke the wrath of the git gods. [https://help.github.com/articles/interactive-rebase](https://help.github.com/articles/interactive-rebase)\n\n### Adding\n```bash\ngit add <list of files>\n``` \n(i.e. ``git add readme.md license.txt``. Can be multiples)\n\n```bash\ngit add --all\n```\nAdd all the new files since last\n\n```bash\ngit add *.txt\n```\nAdd all txt files in directory\n\n### Staging\n```bash\ngit diff\n```\nShow unstaged differences since last commit\n\n```bash\ngit diff --staged\n```\nGets the staged differences and displays what has changed since our last commit\n\n### Reverting\n```bash\ngit reset HEAD <file>\n```\nHead is the last commit on the current branch we are on. What if you stage something you didn't need to be staged? This is the key.\n\n```bash\ngit checkout -- <file>\n```\nReset all changes to a file since last commit\n\n```bash\ngit reset --soft HEAD^\n```\nWhat if you regret a commit? This will undo your last commit. (^ means move commit before HEAD and puts changes into staging).\n\n```bash\ngit reset --hard HEAD^\n```\nTraverse through commits and revert back one by one.\n\n```bash\ngit reset --hard HEAD\n```\nUndo Last commit and all changes\n\n```bash\ngit commit --amend -m \"added another file to the commit'\n```\nNew commit message will override previous commit message\n\n### Remotes\n\"Remotes are kinda like bookmarks\"\n\n```bash\ngit remote -v\n```\nShow the current remote repos\n\n```bash\ngit remote add <name> <address>\n```\nAdd a new remote repo\n\n```bash\ngit remote rm <name>\n```\nRemove remote repo\n\n### Cloning, Branching, Fetching &amp; Merging\n```bash\ngit fetch\n```\nPulls down any changes but doesn't merge them\n\n```bash\ngit branch <branch name>\n```\nMakes a new branch\n\n```bash\ngit checkout <branch name>\n```\nSwitching branch and on a different timeline\n\n```bash\ngit merge <branch>\n```\nMerges branch into master\n\n```bash\ngit branch -d <branch name>\n```\nDeletes branch\n\n```bash\ngit checkout -b <branch name>\n```\nCreates a new branch and then switches to it\n\n```bash\n:wq + enter\n```\nVI Editor Quick Key Exit\n\n```bash\ng fetch origin\n\ngit checkout -t <remote>/<branch>\n```\nFetches a remote branch not available locally [also reference issue #7](https://github.com/grayghostvisuals/Practice-Git/issues/7)\n\n### Pushing &amp; Pulling\n```bash\ngit push -u origin master (remote repo name[origin], local branch name[master])\n``` \nLets you just run git push later on without specifying name and branch\n\n```bash\ngit pull\n```\nPull changes in and syncs up your repo. Doesn't update local code\n\n### Branching\n```bash\ngit branch -r\n```\nList all remote branches\n\n```bash\ngit remote show origin\n```\nShow all the remote branches\n\n```bash\ngit push origin :<branch name>\n```\nDeletes the remote branch\n\n```bash\ngit branch -D <branch name>\n```\nDelete the local repo branch and if you don't want the commits any longer on it then delete them too.\n\n```bash\ngit remote prune origin\n```\nDeletes the branch locally if it has been removed remotely. Helps to remove stale references.\n\n### Rebasing\n\"Merge commits are bad\"\n\n```bash\ngit rebase\n```\nMove all changes to master local which are not in origin/master remote to a temporary area\n\n### History\n```bash\ngit log\n```\nViewing the commits history\n\n```bash\ngit config --global color.ui true\n```\nColor codes the commit SHA\n\n```bash\ngit log --pretty=oneline\n```\n\nor \n\n```bash\ngit log --graph --oneline --all\n```\nCommit and history is one line\n\n```bash\ngit log --pretty=format:\"%h\n```\nExactly how you want the output using placeholders (use git help log)\n\n```bash\ngit log --until <value>\n```\nDate Ranges. For example you could grab everything from the year 2013 using ``git log --until 2013``\n\n### Removal\n```bash\ngit rm <filename>\n```\nRemoves file completely\n\n```bash\ngit rm --cached <file names>\n```\nWon't be deleted from your file system, but keeps the local changes still.\n\n### Help\n```bash\ngit help\n```\n```bash\ngit help <command>\n```\n#### Nasty link\n"
  },
  {
    "path": "branch1502/test-file.txt",
    "content": "some text goes here.\nsome new text edit goes here.\nnope\nyep\n"
  },
  {
    "path": "dimitris_announcement",
    "content": "I'm having a baby girl in March and I'm shouting it at the top of Git mountain!\n"
  },
  {
    "path": "norajs/readme.txt",
    "content": "Thanks yo for the practice project :) Gonna mess around here a little.\n\nNora\nHello\n"
  },
  {
    "path": "practice-git/foo.txt",
    "content": "lorem\n"
  }
]