That’s true. I’m starting to try to remember to do that; it’s just not automatized yet. I’m up to doing it about 30% of the time. 
Now I’ve got this:
Run pnpm install --frozen-lockfile
ERR_PNPM_LOCKFILE_CONFIG_MISMATCH Cannot proceed with the frozen installation. The current "settings.autoInstallPeers" configuration doesn't match the value found in the lockfile
Update your lockfile using "pnpm install --no-frozen-lockfile"
So then I did what it told me, and now I get:
Run bundle install
Don't run Bundler as root. Installing your bundle as root will break this
application for all non-root users on this machine.
Could not locate Gemfile
But when I do this:
(main *) pfaffman@noreno:~/src/pfaffman/discourse-custom-homepage-for-groups$ cp ~/src/discourse-repos/discourse-theme-skeleton/pnpm-lock.yaml .
(main *) pfaffman@noreno:~/src/pfaffman/discourse-custom-homepage-for-groups$ git add pnpm-lock.yaml
(main +) pfaffman@noreno:~/src/pfaffman/discourse-custom-homepage-for-groups$ git commit -m 'their pnpm lock'
[main e195a2e] their pnpm lock
1 file changed, 1 insertion(+), 1 deletion(-)
(main) pfaffman@noreno:~/src/pfaffman/discourse-custom-homepage-for-groups$ git push
and I’m sure their repo is up to date.
See? And it even is reminding me that I’m irresponsibly working on the main branch.