Skip to content

Add the shared pull-request template (taphouse sync) - #2

Merged
tap merged 1 commit into
mainfrom
claude/repository-inconsistencies-nkocvd
Jul 27, 2026
Merged

Add the shared pull-request template (taphouse sync)#2
tap merged 1 commit into
mainfrom
claude/repository-inconsistencies-nkocvd

Conversation

@tap

@tap tap commented Jul 27, 2026

Copy link
Copy Markdown
Owner

Syncs the new canonical pull-request template from TapHouse (see tap/TapHouse#5, which adds it to the canonical set and to scripts/sync.sh). None of the 13 family repos had one.

Single file, no code or CI changes.

The template asks for what changed and why, a Verification section stating what was actually built and run versus what CI will gate (plus the family's measured-not-remembered rule for performance claims), and a delete-what-does-not-apply list of the recurring cross-repo concerns.

Most relevant here is the Max package bullet — reference page and help patcher per object, and the macOS binary staying universal. This repo already gates both in CI, and is in fact the only one in the family that runs ctest on both macOS and Windows, plus an otool -L | grep @rpath/libpython check the others have no equivalent for. Those are worth naming in the Verification prompt if you tailor it.

It is created only-if-missing and deliberately not drift-guarded, so tailoring it won't fail the drift job.

Three unrelated observations from the sweep that produced this, for whenever this repo is next touched:

  • it pins TapHouse drift-check at @v4 while most consumers are on @v5, and carries no .claude/ SessionStart hook
  • C++20 is set per-object on the external only, so the _test target stays at min-api's C++17 and the clang-tidy job is hardcoded to -std=c++17 — the only repo in the family without a central C++20 policy
  • package-info.json.in and the README badges still point at tap/Python-Max, the pre-rename identity

Generated by Claude Code

Synced from the canonical TapHouse copy: the family's shared review prompts --
what changed and why, a Verification section asking what was actually built and
run versus what CI will gate (plus the measured-not-remembered rule for
performance claims), and a delete-what-does-not-apply list of the recurring
cross-repo concerns: contract changes, submodule pin flow, notebook
re-execution, package docs/help and universal binaries, and documented per-repo
exceptions.

Created only-if-missing and deliberately NOT drift-guarded, following the
.claude/settings.json precedent: it is prose for humans rather than a
machine-enforced config, so this repo is free to tailor it -- trim the bullets
that do not apply here.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JhhQ93r2E1QTnCx46YfX8j
@tap
tap merged commit 4484a04 into main Jul 27, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants