Skip to content

Skip product releases for docs-only commits - #118

Merged
kl3inIT merged 1 commit into
mainfrom
fix/product-release-noop-for-docs
Jul 28, 2026
Merged

Skip product releases for docs-only commits#118
kl3inIT merged 1 commit into
mainfrom
fix/product-release-noop-for-docs

Conversation

@kl3inIT

@kl3inIT kl3inIT commented Jul 28, 2026

Copy link
Copy Markdown
Owner

Problem

The independent docs work exposed a remaining coupling: every green docs-only main commit copied all six product image manifests and automatically redeployed the product, even though no product image input changed.

Change

  • treat an empty product-image change set as an explicit no-op
  • skip manifest carry-forward and release verification for no-op runs
  • choose previous bases only from runs whose immutable image-set job actually succeeded
  • make automatic and manual product deploy validation require that same release job, so a successful no-op workflow can never reach SSH
  • record the verified product deployment and docs-absent boundary

Verification

  • actionlint 1.7.12
  • documentation operating-model check (284 Markdown, 8 mirrored domain pairs)
  • git diff --check

This does not dispatch a docs deployment or change DNS/TLS/Nginx Proxy Manager.

@coderabbitai

coderabbitai Bot commented Jul 28, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@kl3inIT, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 36 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 820dda1b-a71d-4d3f-b925-df4e900fa707

📥 Commits

Reviewing files that changed from the base of the PR and between c5d4797 and 49d4e0e.

⛔ Files ignored due to path filters (3)
  • docs/increments/active/2026-07-28-public-docs-portal/plan.md is excluded by !docs/**
  • docs/increments/active/2026-07-28-public-docs-portal/verification.md is excluded by !docs/**
  • docs/runbooks/public-docs-deployment.md is excluded by !docs/**
📒 Files selected for processing (3)
  • .github/workflows/build-images.yml
  • .github/workflows/deploy-production.yml
  • ARCHITECTURE.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/product-release-noop-for-docs

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.

@kl3inIT
kl3inIT merged commit d3acfac into main Jul 28, 2026
14 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.

1 participant