docs(organize): save cleanup idea for later and organize personal first-time stuff to different file

Chasesomero

Mar 7, 2026, 9:28 PM

44YOENACLYYR6MOL3ILKW7S6U6ZIUAAV2HVEAC6CVJKBSWOX5CAAC

Dependencies

• [2] 32ICZXL4 init laravel zero for fun
• [3] PHV2QDRE replace readme with my own notes
• [4] 3JSFZAT5 bit of copilot proofreading and editing
• [5] ZHWYHIOH feat(pijul-qol): have copilot make script to show change messages beside changes, in pijul credit output
• [6] WNLMHTPQ feat(pijul-qol:move-to-zero): two new commands, to try make intent-tag discovery easier
• [7] QFA6RRE2 docs(save pr idea for later): save an idea that sounds similar to pr reviewing to try later
• [8] RVCFE3CZ feat(pijul-qol:zero-live-search): polish functionality to get it to atually working. fix errors, make tests thtually work

Change contents

• replacement in README.md at line 77
  [5.228]→[4.0:26](∅→∅),[7.343]→[4.0:26](∅→∅),[6.8981]→[4.0:26](∅→∅),[2.313020]→[4.0:26](∅→∅)
  − ## First-Time Setup Notes
  [7.343]

  [4.26]
  + ## Cleanup workflow with channels
• replacement in README.md at line 79
  [4.27]→[4.27:61](∅→∅)
  − ### Getting SSH to Work with Nest
  [4.27]

  [2.314298]
  + If you want to do a bigger cleanup pass with a review step at the end, create a base channel and then do the cleanup work on a second channel:
• replacement in README.md at line 81
  [2.314299]→[3.201:378](∅→∅)
  − I never was able to get the SSH on my macbook to work for the Nest website. What changed tonight? I had my Copilot CLI figure it out. I'll have to ask him what the problem was.
  [2.314299]

  [2.314306]
  + ```bash

  + pijul channel new cleanup-base

  + pijul channel new cleanup-pass

  + pijul channel switch cleanup-pass

  + ```
• replacement in README.md at line 87
  [2.314307]→[4.62:241](∅→∅)
  − From my estimation, the problem was my SSH agent wasn't consistently loaded on my terminal sessions. However, it really smells to me like a red herring the CLI agent went off on.
  [2.314307]

  [2.314324]
  + Suggested flow:
• replacement in README.md at line 89
  [2.314325]→[4.242:645](∅→∅)
  − One big thing it found was the correct format for identifying the website to use, the username, and the repo name. I had been using the wrong format, which was causing the SSH connection to fail. The Pijul CLI would only say "error 404", so I was lost. Copilot determined some way to find out more error details, apparently from the Pijul docs (I saw a few Pijul website URLs flash by in the terminal).
  [2.314325]

  [2.314402]
  + - Keep `cleanup-base` unchanged as the comparison point.

  + - Record cleanup changes on `cleanup-pass`.

  + - When you want a review of everything you changed, run `pijul diff --channel cleanup-base`.

  + - Use `pijul log --channel cleanup-base` and `pijul log --channel cleanup-pass` if you want to compare recorded changes by channel.
• replacement in README.md at line 94
  [2.314403]→[4.646:670](∅→∅)
  − ### SSH Key Differences
  [2.314403]

  [2.314483]
  + This gives you a safer place to do a lot of cleanup before reviewing the full pass together.
• replacement in README.md at line 96
  [2.314484]→[4.671:968](∅→∅)
  − One other difference tonight was running from a Chromebook instead of my macbook. I remember something about macbooks using a different SSH key format, and I know my default key here is called `id_rsa` whereas on my macbook it's `id_ed25519` (maybe—that name is just a Copilot auto-completion).
  [2.314484]

  [2.314643]
  + ## Personal first-time setup notes
• replacement in README.md at line 98
  [2.314644]→[4.969:1257](∅→∅),[4.1257]→[2.314655:314656](∅→∅),[3.1884]→[2.314655:314656](∅→∅),[2.314655]→[2.314655:314656](∅→∅),[2.314656]→[4.1258:2058](∅→∅)
  − ### Weird Chromebook Issue

  −

  − A weird thing that happened was, halfway through the process of editing some stuff after my first Pijul push to the Nest, the Chromebook just up and died. Like, as if its battery died. I plugged it in and it came back, but the battery was still above halfway.

  −

  − ## Going Forward

  −

  − ### Editor Setup

  −

  − I'd like to make a few repos to test out working from Pijul. VS Code doesn't have a Pijul extension (that I've found yet), so I'll have to do all my Pijul work from the terminal. I can use VS Code for editing, but I'll have to run the Pijul commands in the terminal. It's not bad, though, especially once I figure out a nice one-letter alias for Pijul.

  −

  − ### Project Considerations

  −

  − Some consideration that goes into what project is good for Pijul is what frameworks/platforms support it. Laravel Zero _might_ be able to publish to the PHP package thing it uses, but I'm not sure. But it's a better chance, I think, than a web app. Although with Laravel Forge, I should be able to just get a server spun up and use a custom deploy script. Install Pijul beforehand.
  [2.314644]
  + See [First-Time Setup Notes for Nest and Pijul](./FIRST_TIME_SETUP_NOTES.md).