Neon LawCall +1 510 800 2090
  • Navigator
  • Notations
  • Legal Aid
  • Sign in

← Using Neon Law Navigator

Use the Project's forge

Chapter 4 of 6 · Section 12 of 24

Sections

1. Why do this

  • 1. Learning objectives
  • 2. The running matter

2. Develop locally

  • 3. Start the local room
  • 4. Sign in

3. Work the litigation matter

  • 5. The four nouns in one workflow
  • 6. One onboarding, one offboarding
  • 7. Walk the retainer intake one question at a time
  • 8. The other notations on a matter
  • 9. Inspect the matter page and its Matter Pages
  • 10. Make a sample-project change

4. Use the Project's forge

  • 11. Git is track changes for the whole folder
  • 12. Optional: work the folder with jj
  • 13. Sign in, then receive repository access
  • 14. Send a change through the same gate
  • 15. Follow the gate and its status

5. Open a real Project

  • 16. Fill the matter-open form
  • 17. Provision the repository and Drive folder — a separate step today
  • 18. Populate the repository
  • 19. Stage a document and sync it
  • 20. Work in a Project with Jujutsu
  • 21. Pull a fresh checkout's documents
  • 22. Matter Pages are a separate, later decision
  • 23. Verify

6. Wrap Up

  • 24. Verify the room

Optional: work the folder with jj

Jujutsu (jj) is a second front end over the same Git repository. The forge, the gate, and protected main still see plain Git; what changes is the attendee's own desk. Every edit is saved as it happens, any step can be undone, and a conflict is recorded in the change instead of stopping work. One command installs jj with Homebrew on macOS, adds it beside .git, and copies the checkout's Git author and signing settings:


navigator project repository jj
jjWhat it is in a matter
ChangeA redline that keeps the same name however often it is revised
BookmarkThe tab on a redline the forge reads as a branch; it stays put until moved
jj undoWithdraw the last step, whatever it was
jj op logThe desk's own docket: every step taken in this checkout, by a person or an agent
Recorded conflictTwo redlines of one sentence, kept side by side until a person decides

A bookmark is the one habit to learn. It does not follow new changes the way a Git branch does, so a push after a revision sends the old one unless the bookmark is moved (jj bookmark set). jj git push --change @ avoids the question: it names a fresh bookmark push/<change-id>, the namespace navigator project repository push already uses.

Presenter notes

Run navigator project repository jj in the sample checkout. Edit a file, then jj st and jj describe -m "why", and push with jj git push --change @; open the pull request from the push/ bookmark on the forge. Repeat the conflict exercise with jj git fetch and jj rebase -d main@origin, and read the conflict in jj log. Revise the change and push without moving its bookmark, so the room sees the stale push, then fix it with jj bookmark set. Finish by deleting a file on purpose, running jj undo, and reading the step back in jj op log.

View all slidesOpen display
← PreviousNext →
Neon Law
  • X opens in a new tab
  • LinkedIn opens in a new tab
  • YouTube opens in a new tab
  • API
  • Blog
  • Contact
  • Design
  • Glossary
  • Navigator
  • Notations
  • Presentations
  • Privacy
  • Team opens in a new tab
  • Terms
  • Testimonials
  • contact@neonlaw.com
  • +1 510 800 2090
  • California
    1515 20th StreetBakersfield, CA 93301
  • Nevada
    5150 Mae Anne AveSte 405-9002Reno, NV 89523
  • New York
    12 E 49th St18th FloorNew York, NY 10017
  • Washington
    1111 Main StSTE 201EVancouver, WA 98660
  • Justice Technology AssociationMission-Aligned Partner opens in a new tab
  • Proud member of Greater Vancouver ChamberGVC opens in a new tab

Attorney advertisement. Nothing here is legal advice without a signed retainer for an active project. Past results do not guarantee future outcomes.

Everyone deserves access to justice.Made with ❤️ in 🗽.

© 2026 Guieb & Shook PC

Powered by neon-law/navigator opens in a new tab26.11.17-rc.1GitHub stars 5