Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jnasbyupgrade wants to merge 1 commit into
base: master
Choose a base branch
from
Open

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -247,7 +247,14 @@ section once resolved.
a behavior change, call it out in `HISTORY.asc` too. (For other files
that are genuinely just internal dev documentation with no bearing on
consumer projects, doc-only changes don't need a `HISTORY.asc` entry.)
7. Everything else is internal by default unless there's a specific
7. **`../pgxntool/POSTGRES-NOTES.asc` and `../pgxntool/CLAUDE-POSTGRES.md`
ship to consumers too, so review them for accuracy — but they never
generate `HISTORY.asc` entries.** They deliberately hold only guidance
about PostgreSQL itself, not about pgxntool, so nothing in them can
describe a pgxntool behavior change. If a claim in either one turns out
to be about pgxntool after all, that's the finding: it belongs in
`README.asc`/`CLAUDE.md` instead.
8. Everything else is internal by default unless there's a specific
indication otherwise.

## Running Skills and Scripts
Expand Down
Loading