···11-## Tooling
22-- If about to perform git actions, check to see if this repo is a [jj] repo. If so,
33-use jj and never use any git commands directly
11+## Version Control
4233+I may use Jujutsu (jj) instead of or alongside Git.
5466-77-[jj]: https://www.jj-vcs.dev/latest/
55+- Before running any version control command, check whether a `.jj` directory exists in the repo root.
66+- If `.jj` is present, NEVER run `git` commands directly (no `git add`, `git commit`, `git checkout`, `git branch`, `git merge`, `git rebase`, etc.) — even though `.jj` repos often have a colocated `.git` directory, using git commands directly can create conflicting state between jj's and git's tracking.
77+- Instead, use the equivalent `jj` commands (e.g. `jj commit`, `jj new`, `jj git push`, `jj bookmark`, etc.).
88+- If you're unsure whether a jj command exists for what you need, ask before falling back to git.
+1-1
dot_npmrc
···44## @lavamoat/allow-scripts
55ignore-scripts=true
66# Avoid installing packages published in last 2 days
77-min-release-age=3
77+#min-release-age=3
88## Don't install packages from git urls, which can
99## be used to bypass the above two settings
1010allow-git=none