uuid:
  - value: 290e62f9-ffc1-4420-91f7-decda6410276
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:07+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: 'No-one sees your clean-up commits'
created:
  - value: '2024-09-02T00:00:00+00:00'
changed:
  - value: '2025-05-11T09:00:07+00:00'
promote:
  - value: false
sticky:
  - value: false
default_langcode:
  - value: true
revision_translation_affected:
  - value: true
path:
  - alias: /daily/2024/09/02/no-one-sees-your-clean-up-commits
    langcode: en
body:
  - value: |
      <p>When you're working on a task - <a href="/daily/2024/08/31/make-it-work-then-make-it-good">whether you're making it work or making it good</a>, you can commit your code changes as often as you like.</p>

      <p>You should definitely commit your changes every time you have a working iteration, even if it's not the complete or final version, or even if the code doesn't pass all the coding standards and static analysis checks.</p>

      <p>Things can be fixed or improved in subsequent commits.</p>

      <p>You can amend or squash commits locally so your clean-up and work-in-progress commits are removed before you push your final version to your remote repository.</p>

      <p>Whilst test-driven development says you should work in small feedback loops and steps, you don't need to push every commit as you wrote them.</p>

      <p>Until you run <code>git push</code>, your commits are yours and yours only.</p>

      <p>You have the opportunity to tidy up and organise your changes - making your commits easier to review and more likely to be approved in a code review.</p>

              
    format: full_html
    processed: |
      <p>When you're working on a task - <a href="http://default/daily/2024/08/31/make-it-work-then-make-it-good">whether you're making it work or making it good</a>, you can commit your code changes as often as you like.</p>

      <p>You should definitely commit your changes every time you have a working iteration, even if it's not the complete or final version, or even if the code doesn't pass all the coding standards and static analysis checks.</p>

      <p>Things can be fixed or improved in subsequent commits.</p>

      <p>You can amend or squash commits locally so your clean-up and work-in-progress commits are removed before you push your final version to your remote repository.</p>

      <p>Whilst test-driven development says you should work in small feedback loops and steps, you don't need to push every commit as you wrote them.</p>

      <p>Until you run <code>git push</code>, your commits are yours and yours only.</p>

      <p>You have the opportunity to tidy up and organise your changes - making your commits easier to review and more likely to be approved in a code review.</p>

              
    summary: null
field_daily_email_cta: {  }