<commit_before><!DOCTYPE html>
<head>
  <title>The Programming Newbie</title>
  <meta charset="UTF-8">
  <link rel="stylesheet" type="text/css" href="your-stylesheet-link-here.css">
</head>
<body>
  <main>
    <h1>The Programming Newbie</h1>
    <h2>Learning the Basics One Commit at a Time</h2>
    <h4>January 24, 2016</h4>

    <section>
      <p>
        What are the benefits of version control?

        Version control is an excellent way for devlopers to keep track of their work.  git, the version control system used on a computer, keeps track of all changes that have been made.  These changes, known as commits, specify when, why and the reason for a change.  Programmers are encouraged to commit early and often, so they can easily acess their code from a particular point in time.

        Another benefit of version control is the ability to recognize errors (known as bugs) that are preventing the code from executing properly.  Programmers can look through their history to see where exactly the error occurred and fix the issue.  In this process, the programmer does not lose the clean, working code because it has been saved in prior commits.

        Lastly, version control is especially useful when working on teams.  Each team member is able to see when specific changes were made and why.  This process helps to reduce redundancy and keep the devopment process moving smoothly.  Version control keeps code efficient and ultimately leads to a successful program.
      </p>
      <p>
        How does git help you keep track of changes?

        Git is the version control system that keeps track of changes on a programmers local machine (computer).  As a new programmer, it is crucial to understand and effictively use git in order to view code at specific points in time.

        The three stages of keeping track of changes in git are modified, staged, and committed.  The first stage, modified, is when there have been changes made to the working directory.  For example, if you have updated a text file with new information, this would be considered modified.  In order to move the modified file to the second stage, staged, the programmer will type in the command: git add <file_name>.  In this second stage, the progammer reviews the code to make sure everything is executing properly before a final save.  To move to the third stage, committed, the programmer will enter the command: git commit -m "type in commit message here".  A file that is committed is the official "saving" of the changes at a particular point in time.

        A programmer is able to view what stage the changes are in via the commands git status and git log.  Git status will show what the current state of the change is.  Some of the comments in git status include added, untracked and staged.  Once a change has been committed, the command git log allows the user to see all of the commits that have been made currently and in the past.  Each commit message in the log shows who completed the commit, the date/time of the commit, and a message of why the commit was made.  Programmers review the git status and git log regularly in order to keep track of their work.
      </p>
      <p>
        Why use GitHub to store your code?

        GitHub is a remote repository that allows programmers to store their code on the cloud.  Because the code is stored remotely, it can be viewed and accessed from any computer.  One of the benefits of storing code in GitHub is that a programmer will still be able to access their code in case of a computer crash.

        When working in teams, GitHub is beneficial because it is an excellent way to collaborate with others.  Each team member is able to access the master code and make changes via a feature branch.  With a feature branch, each programmer can work on their specific piece of code and then have it merged back to the master file.  This process keeps guidelines clear and allows for a review process by all team members.  In addition to sharing code with a team, code on GitHub can be shared within the wider programming community, which encourages the spirit of exploration.
      </p>

        <!-- copy and paste as many sections as you want to add paragraphs -->
      </section>
    </main>
  </body>
  </html><commit_msg>Change title to Version Control and add breaks<commit_after><!DOCTYPE html>
<head>
  <title>Version Control</title>
  <meta charset="UTF-8">
  <link rel="stylesheet" type="text/css" href="your-stylesheet-link-here.css">
</head>
<body>
  <main>
    <h1>Version Control</h1>
    <h2>January 24, 2016</h2>

    <section>
      <p>
        What are the benefits of version control?<br />

        Version control is an excellent way for devlopers to keep track of their work.  git, the version control system used on a computer, keeps track of all changes that have been made.  These changes, known as commits, specify when, why and the reason for a change.  Programmers are encouraged to commit early and often, so they can easily acess their code from a particular point in time.<br />

        Another benefit of version control is the ability to recognize errors (known as bugs) that are preventing the code from executing properly.  Programmers can look through their history to see where exactly the error occurred and fix the issue.  In this process, the programmer does not lose the clean, working code because it has been saved in prior commits.<br />

        Lastly, version control is especially useful when working on teams.  Each team member is able to see when specific changes were made and why.  This process helps to reduce redundancy and keep the devopment process moving smoothly.  Version control keeps code efficient and ultimately leads to a successful program.<br />
      </p>
      <p>
        How does git help you keep track of changes?<br />

        Git is the version control system that keeps track of changes on a programmers local machine (computer).  As a new programmer, it is crucial to understand and effictively use git in order to view code at specific points in time.<br />

        The three stages of keeping track of changes in git are modified, staged, and committed.  The first stage, modified, is when there have been changes made to the working directory.  For example, if you have updated a text file with new information, this would be considered modified.  In order to move the modified file to the second stage, staged, the programmer will type in the command: git add <file_name>.  In this second stage, the progammer reviews the code to make sure everything is executing properly before a final save.  To move to the third stage, committed, the programmer will enter the command: git commit -m "type in commit message here".  A file that is committed is the official "saving" of the changes at a particular point in time.<br />

        A programmer is able to view what stage the changes are in via the commands git status and git log.  Git status will show what the current state of the change is.  Some of the comments in git status include added, untracked and staged.  Once a change has been committed, the command git log allows the user to see all of the commits that have been made currently and in the past.  Each commit message in the log shows who completed the commit, the date/time of the commit, and a message of why the commit was made.  Programmers review the git status and git log regularly in order to keep track of their work.<br />
      </p>
      <p>
        Why use GitHub to store your code?<br />

        GitHub is a remote repository that allows programmers to store their code on the cloud.  Because the code is stored remotely, it can be viewed and accessed from any computer.  One of the benefits of storing code in GitHub is that a programmer will still be able to access their code in case of a computer crash.<br />

        When working in teams, GitHub is beneficial because it is an excellent way to collaborate with others.  Each team member is able to access the master code and make changes via a feature branch.  With a feature branch, each programmer can work on their specific piece of code and then have it merged back to the master file.  This process keeps guidelines clear and allows for a review process by all team members.  In addition to sharing code with a team, code on GitHub can be shared within the wider programming community, which encourages the spirit of exploration.<br />
      </p>

        <!-- copy and paste as many sections as you want to add paragraphs -->
      </section>
    </main>
  </body>
  </html>
{'fraction_non_alphanumeric': 0.04387695879280325, 'fraction_numerical': 0.0027858386535113177, 'mean_word_length': 3.4898384575299635, 'pattern_counts': {'":': 0, '<': 68, '<?xml version=': 0, '>': 68, 'https://': 0, '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': '4349798', 'n_tokens_mistral': 2067, 'n_tokens_neox': 1956, 'n_words': 1370}