Repository navigation
Validate PGXNTOOL_VERIFY_RESULTS_MODE - #132
Merged
jnasbyupgrade merged 3 commits intoOct 7, 2026
Merged
jnasbyupgrade merged 3 commits into
jnasbyupgrade merged 3 commits into
Conversation
Any value other than exactly `pgtap` silently selected `diffs` mode, so a typo such as `pgTap` quietly weakened the `make results` safeguard. - New `pgxntool_validate_choice` helper in `base.mk`: lowercases a single-word value and checks it against an allowed list, otherwise a parse-time `$(error)` naming the variable and the value. - `PGXNTOOL_VERIFY_RESULTS_MODE` now accepts `pgtap` or `diffs` case-insensitively; anything else (including empty) is an error. Mode selection for valid values is unchanged. - README.asc documents the accepted values and case handling; HISTORY.asc gets a STABLE entry. README.html is regenerated (it was already behind README.asc). Related changes in pgxntool-test: - `make-test.bats` covers default, mixed-case, invalid and empty values at the `print-` layer, plus mixed-case recipe selection via `make -n`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
…results-mode # Conflicts: # README.html
jnasbyupgrade
added a commit
to Postgres-Extensions/pgxntool-test
that referenced
this pull request
Oct 7, 2026
This PR adds test coverage for Postgres-Extensions/pgxntool#132, which validates `PGXNTOOL_VERIFY_RESULTS_MODE`. The variable now accepts `pgtap` or `diffs` case-insensitively, and any other value is a parse-time error.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PGXNTOOL_VERIFY_RESULTS_MODEis now validated: it acceptspgtapordiffs, case-insensitively, and any other value is a parse-timemakeerror. Before this, any value other than exactlypgtap(for example the typopgTap) silently selecteddiffsmode and weakened themake resultssafeguard.Merge this PR first, before its paired pgxntool-test PR (link below). This change adds behavior that the pgxntool-test PR's new tests depend on. See pgxntool-test's CLAUDE.md, "Merge Order for Paired PRs".
Changes
base.mk: newpgxntool_validate_choicehelper. It lowercases a single-word value, checks it against an allowed list, and otherwise calls$(error)with the variable name and the value it got. It uses the same case handling aspgxntool_validate_yesno, which is unchanged.PGXNTOOL_VERIFY_RESULTS_MODEis normalized through that helper. An empty value is rejected too. Valid values select the same mode as before.README.ascdocuments the accepted values and case handling, both in the verify-results safeguard section and in the Configuration Variables entry.HISTORY.aschas a new STABLE entry. There is no issue number, so the "Issues fixed" line is unchanged.README.htmlis regenerated. It was already behindREADME.ascon master (thecheck-duplicate-docssection was missing), so the diff includes that catch-up as well as this change.Sibling sites checked
base.mk: the comment block for the variable is updated.ifeq ($(PGXNTOOL_VERIFY_RESULTS_MODE),pgtap)is unaffected, because it now sees the normalized value.README.asc: the= diffs # or pgtapexample is unaffected.HISTORY.asc: the existing mention under themake resultsfix is unaffected.CLAUDE.md: does not mention the variable.Conflict note
Open PRs #129 and #130 also regenerate
README.html, so whichever of them merges later will conflict on that file. Resolve it by regeneratingREADME.html, not by hand-merging.HISTORY.ascandREADME.ascmerge cleanly against #128, #129 and #130.Paired pgxntool-test PR: Postgres-Extensions/pgxntool-test#99
🤖 Generated with Claude Code