oliverdavies.uk/content/node.fe407991-a896-410c-9223-51a7ad43d4d2.yml

uuid:
  - value: fe407991-a896-410c-9223-51a7ad43d4d2
langcode:
  - value: en
type:
  - target_id: daily_email
    target_type: node_type
    target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
revision_timestamp:
  - value: '2025-05-11T09:00:05+00:00'
revision_uid:
  - target_type: user
    target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
revision_log: {  }
status:
  - value: true
uid:
  - target_type: user
    target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
title:
  - value: 'Always review your changes'
created:
  - value: '2024-10-25T00:00:00+00:00'
changed:
  - value: '2025-05-11T09:00:05+00:00'
promote:
  - value: false
sticky:
  - value: false
default_langcode:
  - value: true
revision_translation_affected:
  - value: true
path:
  - alias: /daily/2024/10/25/always-review-your-changes
    langcode: en
body:
  - value: |
      <p><a href="/daily/2024/10/24/git-stash-is-underrated">In yesterday's email</a> where I wrote about <code>git stash</code>, I mentioned the <code>-p</code> or <code>--patch</code> options.</p>

      <p>When stashing changes, this allows you to interactively select which changes you want to stash and what you don't.</p>

      <p>This is supported by other Git commands, including <code>git add</code>.</p>

      <p>I always use <code>git add -p</code> when adding changes as it gives me the chance to review them before committing them.</p>

      <p>If I left any stray comments, debug code, trailing spaces or anything I don't want to commit, I can remove them.</p>

      <p>If I was working on multiple changes (which I avoid), I can select the appropriate changes and create commits related to each change to keep the history clean and useful.</p>

      <p>I also use <code>git diff</code> and <code>git diff --staged</code> to review changes as well as <code>git show</code> to review commits.</p>

      <p>By doing this, I know my commits will be in the best state for others to review now or for me to review if I need to in the future.</p>

              
    format: full_html
    processed: |
      <p><a href="/daily/2024/10/24/git-stash-is-underrated">In yesterday's email</a> where I wrote about <code>git stash</code>, I mentioned the <code>-p</code> or <code>--patch</code> options.</p>

      <p>When stashing changes, this allows you to interactively select which changes you want to stash and what you don't.</p>

      <p>This is supported by other Git commands, including <code>git add</code>.</p>

      <p>I always use <code>git add -p</code> when adding changes as it gives me the chance to review them before committing them.</p>

      <p>If I left any stray comments, debug code, trailing spaces or anything I don't want to commit, I can remove them.</p>

      <p>If I was working on multiple changes (which I avoid), I can select the appropriate changes and create commits related to each change to keep the history clean and useful.</p>

      <p>I also use <code>git diff</code> and <code>git diff --staged</code> to review changes as well as <code>git show</code> to review commits.</p>

      <p>By doing this, I know my commits will be in the best state for others to review now or for me to review if I need to in the future.</p>

              
    summary: null
field_daily_email_cta: {  }