<commit_before>---
layout: slide-deck
title: "Version control & GitHub"
desc: "Explaining different version control systems, what their purpose is, and how they work."

slides:
  - type: super-big-text
    content: |
      **Version control & GitHub**

  - content: |
      ## Permanent undo & collaboration

      - Permanent undo states—move backwards in time
      - Opt into the undo—not automatic
      - Keep track what each other did
      - Automatically merge changes

  - content: |
      ## Solutions

      - *Dropbox* — for big files, Creative Suite
      - *InVision* — for UX files, wireframes, prototypes
      - *GitHub* — for code, text files, small images

  - content: |
      ## Why GitHub?

      - Used professionally
      - Can see each other’s code & comment
      - Free web hosting

  - content: |
      ## Process

      1. Make the repository
      2. Clone to your computer
      3. Write code, test & make commits
      4. Sync to GitHub
      5. See live website

  - content: |
      ## Commit to save state

      - Commit when you’ve done something significant
        <br>*Add the navigation; Style the footer; Fix a bug*
      - Every commit needs a message describing what changed
      - **Commit often!**
      - It’s a habit you’ll have to form

  - content: |
      ## Commit message best practices

      1. Minimum 3 words & 10 characters
      2. Proper spelling & grammar
        <br>Capital starting letter, no period
      3. Must start with an imperative verb
        <br>*Create*, *Fix*, *Add*, *Solve*, etc.

      Pretend every commit starts with the phrase: **“This commit will…”**

  - content: |
      ## Bad commit messages

      “asdf”

      “chanegs”

      “Commit”

      “Fix”

  - content: |
      ## Good commit messages

      “Create the basic index.html”

      “Add the navigation”

      “Fix a bug in the footer”

  - content: |<commit_msg>Reorder slides to follow how I actually like to present them<commit_after>---
layout: slide-deck
title: "Version control & GitHub"
desc: "Explaining different version control systems, what their purpose is, and how they work."

slides:
  - type: super-big-text
    content: |
      **Version control & GitHub**

  - content: |
      ## Permanent undo & collaboration

      - Permanent undo states—move backwards in time
      - Opt into the undo—not automatic
      - Keep track what each other did
      - Automatically merge changes

  - content: |
      ## Solutions

      - *Dropbox* — for big files, Creative Suite
      - *InVision* — for UX files, wireframes, prototypes
      - *GitHub* — for code, text files, small images

  - content: |
      ## Why GitHub?

      - Used professionally
      - Can see each other’s code & comment
      - Free web hosting

  - content: |
      ## Process

      1. Make the repository
      2. Clone to your computer
      3. Write code, test & make commits
      4. Sync to GitHub
      5. See live website

  - content: |
      ## Commit to save state

      - Commit when you’ve done something significant
        <br>*Add the navigation; Style the footer; Fix a bug*
      - Every commit needs a message describing what changed
      - **Commit often!**
      - It’s a habit you’ll have to form

  - content: |
      ## Commit message best practices

      1. Minimum 3 words & 10 characters
      2. Proper spelling & grammar
        <br>Capital starting letter, no period
      3. Must start with an imperative verb
        <br>*Create*, *Fix*, *Add*, *Solve*, etc.

      Pretend every commit starts with the phrase: **“This commit will…”**

  - content: |
      ## Good commit messages

      “Create the basic index.html”

      “Add the navigation”

      “Fix a bug in the footer”

  - content: |
      ## Bad commit messages

      “asdf”

      “chanegs”

      “Commit”

      “Fix”

  - content: |
{'fraction_non_alphanumeric': 0.08989925083957634, 'fraction_numerical': 0.005683285972616895, 'mean_word_length': 2.120064464141821, 'pattern_counts': {'":': 0, '<': 9, '<?xml version=': 0, '>': 9, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7118328', 'n_tokens_mistral': 1150, 'n_tokens_neox': 1055, 'n_words': 450}