Repository navigation
Add hosted check hint to CI failures - #3
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b65e023544
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| .option('--min-pg-version <version>', 'Minimum PostgreSQL version to assume', '14') | ||
| .option('--max-risk <risk>', 'Maximum allowed risk level for CI mode', 'high') | ||
| .option('--ci', 'CI mode: exit 1 if max risk exceeded', false) | ||
| .option('--no-cloud-hint', 'Do not print the pgfence Cloud hint when CI blocks') |
There was a problem hiding this comment.
Apply the Cloud hint to trace CI failures
The documented pgfence trace --ci path also blocks with exit 1 for risk, trace errors, or mismatches (src/index.ts lines 763–770), but the new option and hint are registered only for analyze. Consequently, trace CI failures never show the advertised hint, and passing --no-cloud-hint to trace is rejected as an unknown option. Register the suppression option and emit the hint at the trace CI gate as well.
Useful? React with 👍 / 👎.
Summary
Verification