<commit_before><!DOCTYPE html>
<head>
  <title>Your page title here</title>
  <meta charset="UTF-8">
  <link rel="stylesheet" type="text/css" href="your-stylesheet-link-here.css">
</head>

<main>
  <h1>Version Control, git, and GitHub</h1>
  <h4>10.26.2014</h4>
  <section>
    <h2>rough drafts for programming</h2>
      <p>
        Version control is a way for anyone to keep track of all the steps they've taken on a creative project on a computer. "Version control" is particularly popular with programmers, but it's an idea you may have come across as early as elementary school. If you ever had to turn in an outline for a short essay, then turn in a rough draft, and lastly a final version, you essentially broke a task down into parts, had copies of your work on each step, and then completed the task. When you're working on a computer, <b>version control makes it easy to track all your changes on a project</b>. It protects each stage, and lets you reference each change at any point.
      </p>
    <h2>get on the git train</h2>
      <p>
        Version control is a method to record all your changes, edits, and versions of a project; git is a program that helps you do it. git organizes changes that you make on your project into different branches. The branch that you want to be as finalized as possible is called 'master'. But what about if you want to test out an idea without overwriting it to the finalized, 'master' branch? That's the beauty of branches on git— you can make one any time you like, test out all your changes, and if you approve them for the final version, you can merge your new, temporary branch with the master version.
      </p>
      <p>That's an overview of how git's software is structured to save all potential changes to a project. git is also incredibly good at tracking as many steps as you want on each branch of each project. When you want to track these steps with git, 3 things have to happen:
        <ol>
          <li>you make a change to a file</li>
          <li>stage the file to be committed</li>
          <li>commit the changes</li>
        </ol>
      When you commit the changes, your changes are saved by git using a unique commit number, so you can go back and find it forevermore.
      </p>
    <h2>the social coding network</h2>
      <p>
        Kazaa meevee eduvant gsnap movity kosmix kazaa klout jumo, trulia unigo groupon wakoopa spock knewton glogster heroku oooj, ning imvu appjet eskobo zillow twitter rovio. Glogster chegg voxy greplin dopplr voki foodzie xobni weebly odeo, sococo zynga knewton loopt palantir lala blyve tumblr blekko, twones akismet plaxo kippt meebo zillow zooomr insala. Oovoo imeem napster divvyshot zinch imeem voxy shopify, fleck kazaa zinch lanyrd boxbe joost wakoopa nuvvo, orkut elgg heekya sifteo scribd napster. Yammer yoono groupon dopplr cloudera nuvvo eduvant klout, voxy groupon disqus eduvant oooj greplin.
      </p><commit_msg>edit p2 text on commits; add p3 text on GitHub<commit_after><!DOCTYPE html>
<head>
  <title>Your page title here</title>
  <meta charset="UTF-8">
  <link rel="stylesheet" type="text/css" href="your-stylesheet-link-here.css">
</head>

<main>
  <h1>Version Control, git, and GitHub</h1>
  <h4>10.26.2014</h4>
  <section>
    <h2>rough drafts for programming</h2>
      <p>
        Version control is a way for anyone to keep track of all the steps they've taken on a creative project on a computer. "Version control" is particularly popular with programmers, but it's an idea you may have come across as early as elementary school. If you ever had to turn in an outline for a short essay, then turn in a rough draft, and lastly a final version, you essentially broke a task down into parts, had copies of your work on each step, and then completed the task. When you're working on a computer, <b>version control makes it easy to track all your changes on a project</b>. It protects each stage, and lets you reference each change at any point.
      </p>
    <h2>get on the git train</h2>
      <p>
        Version control is a method to record all your changes, edits, and versions of a project; git is a program that helps you do it. git organizes changes that you make on your project into different branches. The branch that you want to be as finalized as possible is called 'master'. But what about if you want to test out an idea without overwriting it to the finalized, 'master' branch? That's the beauty of branches on git— you can make one any time you like, test out all your changes, and if you approve them for the final version, you can merge your new, temporary branch with the master version.
      </p>
      <p>
        That's an overview of how git's software is structured to save all potential changes to a project. git is also incredibly good at tracking as many steps as you want on each branch of each project. When you want to track these steps with git, 3 things have to happen:
          <ol>
            <li>you make a change to a file</li>
            <li>you stage the file to be committed</li>
            <li>you commit the changed file with a message describing the change</li>
          </ol>
        "Staging a file" means adding it to a list to be included in the next commit. "Committing" means your changes are saved by git using a unique number, so you can go back and find that save point forevermore. That change is now saved (and you know why you made the change, thanks to the message).
      </p>
    <h2>the social coding network</h2>
      <p>
        So, git is a program on your computer that you can use to track changes. Thanks to so many people and programmers using it to track and protect their projects, a lot of them have wanted to get together to talk about it on the internet, and the place that they do that is called <a href="https://github.com/">GitHub</a>.
      </p>
      <p>
        GitHub is a website that you can use to upload your project as a backup, and you can share it with a community that can help you refine if you like. GitHub's social nature makes it possible for people all over the world to look at and access a project, which also makes it an incredibly powerful tool for collaboration.
      </p>
{'fraction_non_alphanumeric': 0.05986482137109752, 'fraction_numerical': 0.0067589314451239136, 'mean_word_length': 3.3953323903818955, 'pattern_counts': {'":': 0, '<': 81, '<?xml version=': 0, '>': 81, 'https://': 1, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2701546', 'n_tokens_mistral': 1739, 'n_tokens_neox': 1676, 'n_words': 988}