<commit_before><!DOCTYPE html>
<head>
  <title>Week 1 First Blog Post</title>
  <meta charset="UTF-8">
  <link rel="stylesheet" type="text/css" href="your-stylesheet-link-here.css">
</head>

<main>
  <h1>How I Learned to Git</h1>
  <h2>not as confusing as it seems</h2>
  <h4>December 6, 2015</h4>

  <section>
    <p>
      So this is week 1 of Dev Bootcamp's Phase 0 and I've learned several things I didn't know before. I've learned how to actually use my command line. Prior to this I simply copied and pasted from the web whenever the need arose and just put faith in the commands people were giving me. Now I can actually, albeit not master level, understand what such commands do - somewhat. One of things I got most excited to say I know how to use now is git and GitHub.
    </p>
    <p>
        I've made several games in the past with GM:S and I've always kept my project files local or on Dropbox for those times I may not have access to my home pc. I practiced a sort of "version control" before I even knew what actual "version control" was by appending my main project folder with v1, v2, etc. It was effective for what I was doing, but I did run into issues like accidentally deleting or overwriting important files without a backup or running into game breaking bugs in which I didn't have an appropriate v# backup. I knew almost from the start that GitHub existed but like many people out there didn't truly know what it was for. I knew it was some collaborative system in which the real programmers hammered out their projects. I wasn't a programmer, just a dabbler in the programming world so I never ventured into GitHub - heck, I didn't even know what the difference between git and GitHub was. But now I do, and I understand just how useful it is.
    </p>
    <p>
        Version control allows developers to know what, when, and where changes to their code was made. Git and GitHub allow for multiple developers to share in the development of a project without stepping on each other's toes or creating conflicting files. In git you have a master project file and whenever you want to make changes, add a feature, or edit the project for whatever reason you create a copy or a branch of the master to work on. Once you've finished your work or added that feature, you then merge that copy/branch onto the master to once again have a single complete project.
    </p>

      <!-- copy and paste as many sections as you want to add paragraphs -->
  </section>
</main><commit_msg>Add first blog pos for week 1 of phase 0<commit_after><!DOCTYPE html>
<head>
  <title>Week 1 First Blog Post</title>
  <meta charset="UTF-8">
  <link rel="stylesheet" type="text/css" href="your-stylesheet-link-here.css">
</head>

<main>
  <h1>How I Learned to Git</h1>
  <h2>not as confusing as it seems</h2>
  <h4>December 6, 2015</h4>

  <section>
    <p>
      So this is week 1 of Dev Bootcamp's Phase 0 and I've learned several things I didn't know before. I've learned how to actually use my command line. Prior to this I simply copied and pasted from the web whenever the need arose and just put faith in the commands people were giving me. Now I can actually, albeit not master level, understand what such commands do - somewhat. One of things I got most excited to say I know how to use now is git and GitHub.
    </p>
    <p>
        I've made several games in the past with GM:S and I've always kept my project files local or on Dropbox for those times I may not have access to my home pc. I practiced a sort of "version control" before I even knew what actual "version control" was by appending my main project folder with v1, v2, etc. It was effective for what I was doing, but I did run into issues like accidentally deleting or overwriting important files without a backup or running into game breaking bugs in which I didn't have an appropriate v# backup. I knew almost from the start that GitHub existed but like many people out there didn't truly know what it was for. I knew it was some collaborative system in which the real programmers hammered out their projects. I wasn't a programmer, just a dabbler in the programming world so I never ventured into GitHub - heck, I didn't even know what the difference between git and GitHub was. But now I do, and I understand just how useful it is.
    </p>
    <p>
        Version control allows developers to know what, when, and where changes to their code was made. Git and GitHub allow for multiple developers to share in the development of a project without stepping on each other's toes or creating conflicting files. In git you have a master project file and whenever you want to make changes, add a feature, or edit the project for whatever reason you create a copy or a branch of the master to work on. Once you've finished your work or added that feature, you then merge that copy/branch onto the master to once again have a single complete project.
    </p>
    <p>
        GitHub gives your project a place to live online where a master branch will always exist and changes can be tracked. It's awesome once you get started!
    </p>

      <!-- copy and paste as many sections as you want to add paragraphs -->
  </section>
</main>
{'fraction_non_alphanumeric': 0.053763440860215055, 'fraction_numerical': 0.0069124423963133645, 'mean_word_length': 3.646743978590544, 'pattern_counts': {'":': 0, '<': 53, '<?xml version=': 0, '>': 53, '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': '7267720', 'n_tokens_mistral': 1372, 'n_tokens_neox': 1281, 'n_words': 875}