Back to the lesson

Original working file

public/blog/keep-a-working-copy.html

Code and working example pages keep their original identifiers and sample text. The lesson and file guidance explain them in your language.

<!doctype html>
<html lang="en">
  <head>
    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width,initial-scale=1" />
    <title>Keep a working copy before a change</title>
    <link rel="stylesheet" href="../style.css" />
  </head>
  <body>
    <main>
      <h1>Keep a working copy before a change</h1>
      <nav><a href="../index.html">All notes</a></nav>
      <article>
        <p>Practice Author · <time datetime="2026-11-15">15 November 2026</time></p>
        <p>A known working revision makes recovery possible.</p>
        <p>
          Before changing a working contact form, save the current revision with Git and
          record a successful test.
        </p>
        <p>
          Make the new change in a separate branch. Compare the preview against the same
          test before merging.
        </p>
        <p>
          If the release fails, recover the working revision and investigate in the
          branch. Recovery and finding the root cause are different jobs.
        </p>
      </article>
    </main>
  </body>
</html>