<feed xmlns='http://www.w3.org/2005/Atom'>
<title>tailscale/misc/git_hook, branch awly/deadcode-linuxfwtest</title>
<subtitle>The easiest, most secure way to use WireGuard and 2FA</subtitle>
<id>http://git.waynecole.info/tailscale/atom?h=awly%2Fdeadcode-linuxfwtest</id>
<link rel='self' href='http://git.waynecole.info/tailscale/atom?h=awly%2Fdeadcode-linuxfwtest'/>
<link rel='alternate' type='text/html' href='http://git.waynecole.info/tailscale/'/>
<updated>2026-04-21T15:42:53Z</updated>
<entry>
<title>misc/git_hook: fix building git_hook in a nested worktree (#19473)</title>
<updated>2026-04-21T15:42:53Z</updated>
<author>
<name>Fernando Serboncini</name>
<email>fserb@tailscale.com</email>
</author>
<published>2026-04-21T15:42:53Z</published>
<link rel='alternate' type='text/html' href='http://git.waynecole.info/tailscale/commit/?id=1669b0d3d48310e970fb55460af34527d7bde602'/>
<id>urn:sha1:1669b0d3d48310e970fb55460af34527d7bde602</id>
<content type='text'>
When the repo is checked out as a nested worktree, a go.work in the
outer tree hijacks module resolution, which makes the rebuild fails
with "main module does not contain package." Set GOWORK=off for the
build since the hook is self-contained.

Bumps HOOK_VERSION so existing installs pick up the fix.

Updates #cleanup

Change-Id: Ibd14849efc26e4e1893c5b8e300caa71573f54bd

Signed-off-by: Fernando Serboncini &lt;fserb@fserb.com.br&gt;</content>
</entry>
<entry>
<title>misc/git_hook: extract shared githook package; auto-rebuild on version bump (#19440)</title>
<updated>2026-04-17T20:24:39Z</updated>
<author>
<name>Fernando Serboncini</name>
<email>fserb@tailscale.com</email>
</author>
<published>2026-04-17T20:24:39Z</published>
<link rel='alternate' type='text/html' href='http://git.waynecole.info/tailscale/commit/?id=514d7d28e799a4ef5d829c4d966c8fff6c3e7cdb'/>
<id>urn:sha1:514d7d28e799a4ef5d829c4d966c8fff6c3e7cdb</id>
<content type='text'>
Pull the hook logic into a reusable githook library package so
tailscale/corp can share it via a thin wrapper main instead of
keeping a forked copy in sync.

The install flow also changes: a wrapper scripts now build the
binary and reinstall the git hooks. Pulling new shared code no
longer requires re-running the installer.

Updates tailscale/corp#39860

Change-Id: I4d606d11c8c883015c190c54e3387a7f9fe4dd32

Signed-off-by: Fernando Serboncini &lt;fserb@tailscale.com&gt;</content>
</entry>
<entry>
<title>misc: add install-git-hooks.go and git hook for Change-Id tracking</title>
<updated>2026-04-08T22:10:53Z</updated>
<author>
<name>Brad Fitzpatrick</name>
<email>bradfitz@tailscale.com</email>
</author>
<published>2026-04-05T02:46:16Z</published>
<link rel='alternate' type='text/html' href='http://git.waynecole.info/tailscale/commit/?id=647deed2d987e747d68f026a551ea45285852b89'/>
<id>urn:sha1:647deed2d987e747d68f026a551ea45285852b89</id>
<content type='text'>
Add misc/install-git-hooks.go and misc/git_hook/ to the OSS repo,
adapted from the corp repo. The primary motivation is Change-Id
generation in commit messages, which provides a persistent identifier
for a change across cherry-picks between branches.

The installer uses "git rev-parse --git-common-dir" instead of go-git
to find the hooks directory, avoiding a new direct dependency while
still supporting worktrees.

Hooks included:
- commit-msg: adds Change-Id trailer
- pre-commit: blocks NOCOMMIT / DO NOT SUBMIT markers
- pre-push: blocks local-directory replace directives in go.mod
- post-checkout: warns when the hook binary is outdated

Also update docs/commit-messages.md to reflect that Change-Id is no
longer optional in the OSS repo.

Updates tailscale/corp#39860

Change-Id: I09066b889118840c0ec6995cc03a9cf464740ffa
Signed-off-by: Brad Fitzpatrick &lt;bradfitz@tailscale.com&gt;
</content>
</entry>
</feed>
