Skip to content

CLAUDE.md: put pgxntool's new PostgreSQL-only docs in the API-surface list - #81

Open
jnasbyupgrade wants to merge 1 commit into
Postgres-Extensions:masterfrom
jnasbyupgrade:docs-superuser-trusted
Open

CLAUDE.md: put pgxntool's new PostgreSQL-only docs in the API-surface list#81
jnasbyupgrade wants to merge 1 commit into
Postgres-Extensions:masterfrom
jnasbyupgrade:docs-superuser-trusted

Conversation

@jnasbyupgrade

Copy link
Copy Markdown
Contributor

Paired with Postgres-Extensions/pgxntool#113, which adds POSTGRES-NOTES.asc and CLAUDE-POSTGRES.md to pgxntool.

Both new files ship to consumers via subtree, so the /release skill's API-documentation review must look at them — the same reasoning that already puts ../pgxntool/CLAUDE.md in scope (item 6). But unlike CLAUDE.md, neither can ever produce a HISTORY.asc entry: they deliberately hold only guidance about PostgreSQL itself, so nothing in them describes a pgxntool behavior change.

The new item 7 says exactly that, and adds the corollary: if a claim in either file turns out to be about pgxntool after all, that is the finding — it belongs in README.asc/CLAUDE.md instead. The old item 7 ("everything else is internal by default") becomes item 8; nothing references these by number.

Doc-only; no test changes.

🤖 Generated with Claude Code

… list

Postgres-Extensions/pgxntool@adb7792 adds
`POSTGRES-NOTES.asc` and `CLAUDE-POSTGRES.md` to pgxntool. Both ship to
consumers via subtree, so the release review must look at them, but neither
can ever produce a `HISTORY.asc` entry: they hold only guidance about
PostgreSQL itself, so nothing in them describes pgxntool behavior. A claim in
either file that turns out to be about pgxntool is itself the finding -- it
belongs in `README.asc`/`CLAUDE.md` instead.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 29, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 7e4e4652-fe82-4f75-a6e5-05e2b686c804

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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.

1 participant