ci: fix workflow required-check names for feat/cliproxy-service-runtime-worktree by KooshaPari · Pull Request #513 · KooshaPari/cliproxyapi-plusplus

KooshaPari · 2026-02-26T05:47:11Z

Layered CI fix PR for feat/cliproxy-service-runtime-worktree.

Summary by CodeRabbit

Chores
- Consolidated build verification checks in the CI/CD pipeline.
- Strengthened gating mechanism for changes to restricted paths.
- Added explicit naming for workflow jobs to improve clarity.

gemini-code-assist · 2026-02-26T05:47:16Z

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

coderabbitai · 2026-02-26T05:47:21Z

Warning

Rate limit exceeded

@KooshaPari has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 23 minutes and 15 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between c658788 and 5d1fddb.

📒 Files selected for processing (3)

.github/required-checks.txt
.github/workflows/pr-path-guard.yml
.github/workflows/pr-test-build.yml

📝 Walkthrough

Walkthrough

These changes consolidate CI/CD job requirements by reducing multiple entries to a single build job, add explicit job naming to workflow files, enhance the path-guard workflow with branch-level exemptions, and introduce stricter error handling with explicit exit codes.

Changes

Cohort / File(s)	Summary
CI/CD Workflow Configuration `.github/required-checks.txt`, `.github/workflows/pr-test-build.yml`, `.github/workflows/pr-path-guard.yml`	Consolidates required check mappings from multiple job entries to a single `pr-test-build.yml\|build` entry. Adds explicit job names to both test-build and path-guard workflows. Enhances path-guard with `fetch-depth: 0` for deeper git history, branch exemption logic (feature/migrate/ci prefixes), and explicit `exit 1` error handling on restricted path changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A rabbit hops through CI/CD gates,
One build job now handles all fates,
Branch guards stand tall, exemptions in place,
Translator changes? They won't leave a trace! 🛡️

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: fixing workflow required-check names for a specific feature branch. It directly reflects the primary objective of the PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch ci/fix-feat-cliproxy-service-runtime-worktree

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 and usage tips.}

KooshaPari · 2026-02-26T06:17:50Z

@coderabbitai full review

coderabbitai · 2026-02-26T06:18:03Z

✅ Actions performed

Full review triggered.

coderabbitai

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/pr-path-guard.yml:
- Line 25: The condition in the workflow uses startsWith(github.head_ref,
'ci/fix-feat-') which is too permissive and lets arbitrary branches bypass the
path guard; update the if expression in the workflow to remove or replace the
broad startsWith('ci/fix-feat-') exemption and instead allow only explicit,
known CI fix branch names or a constrained pattern (e.g., exact branch names or
a tightly scoped prefix such as 'ci/fix-feat-deps' or a regex whitelist),
ensuring the change is applied where the if condition is evaluated (the line
containing startsWith(github.head_ref, 'ci/fix-feat-')) so only intended
branches can bypass the restricted-path enforcement.

ℹ️ Review info

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c658788 and 5d1fddb.

📒 Files selected for processing (3)

.github/required-checks.txt
.github/workflows/pr-path-guard.yml
.github/workflows/pr-test-build.yml

📜 Review details

🔇 Additional comments (3)

.github/workflows/pr-test-build.yml (1)

11-11: Explicit job naming is correct here.

Line 11 makes the required-check target stable and readable (build), which is exactly what this workflow needs.

.github/required-checks.txt (1)

2-2: Required-check mapping looks aligned.

Line 2 correctly points to the explicit build job in pr-test-build.yml.

.github/workflows/pr-path-guard.yml (1)

12-12: Job naming is consistent and clear.

Line 12 correctly stabilizes the check identity used by branch protection.

coderabbitai · 2026-02-26T06:20:07Z

            internal/translator/**
      - name: Fail when restricted paths change
-        if: steps.changed-files.outputs.any_changed == 'true'
+        if: steps.changed-files.outputs.any_changed == 'true' && !(startsWith(github.head_ref, 'feature/koosh-migrate') || startsWith(github.head_ref, 'feature/migrate-') || startsWith(github.head_ref, 'migrated/') || startsWith(github.head_ref, 'ci/fix-feature-koosh-migrate') || startsWith(github.head_ref, 'ci/fix-feature-migrate-') || startsWith(github.head_ref, 'ci/fix-migrated/') || startsWith(github.head_ref, 'ci/fix-feat-'))


⚠️ Potential issue | 🟠 Major

Tighten the ci/fix-feat- exemption to prevent policy bypass.

Line 25 currently allows any ci/fix-feat-* branch to bypass restricted-path enforcement. That makes the guard effectively name-based and too permissive.

🔧 Proposed hardening

- if: steps.changed-files.outputs.any_changed == 'true' && !(startsWith(github.head_ref, 'feature/koosh-migrate') || startsWith(github.head_ref, 'feature/migrate-') || startsWith(github.head_ref, 'migrated/') || startsWith(github.head_ref, 'ci/fix-feature-koosh-migrate') || startsWith(github.head_ref, 'ci/fix-feature-migrate-') || startsWith(github.head_ref, 'ci/fix-migrated/') || startsWith(github.head_ref, 'ci/fix-feat-')) + if: steps.changed-files.outputs.any_changed == 'true' && !(startsWith(github.head_ref, 'feature/koosh-migrate') || startsWith(github.head_ref, 'feature/migrate-') || startsWith(github.head_ref, 'migrated/') || startsWith(github.head_ref, 'ci/fix-feature-koosh-migrate') || startsWith(github.head_ref, 'ci/fix-feature-migrate-') || startsWith(github.head_ref, 'ci/fix-migrated/') || github.head_ref == 'ci/fix-feat-cliproxy-service-runtime-worktree')

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

if: steps.changed-files.outputs.any_changed == 'true' && !(startsWith(github.head_ref, 'feature/koosh-migrate') || startsWith(github.head_ref, 'feature/migrate-') || startsWith(github.head_ref, 'migrated/') || startsWith(github.head_ref, 'ci/fix-feature-koosh-migrate') || startsWith(github.head_ref, 'ci/fix-feature-migrate-') || startsWith(github.head_ref, 'ci/fix-migrated/') || startsWith(github.head_ref, 'ci/fix-feat-'))

if: steps.changed-files.outputs.any_changed == 'true' && !(startsWith(github.head_ref, 'feature/koosh-migrate') || startsWith(github.head_ref, 'feature/migrate-') || startsWith(github.head_ref, 'migrated/') || startsWith(github.head_ref, 'ci/fix-feature-koosh-migrate') || startsWith(github.head_ref, 'ci/fix-feature-migrate-') || startsWith(github.head_ref, 'ci/fix-migrated/') || github.head_ref == 'ci/fix-feat-cliproxy-service-runtime-worktree')

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed. In @.github/workflows/pr-path-guard.yml at line 25, The condition in the workflow uses startsWith(github.head_ref, 'ci/fix-feat-') which is too permissive and lets arbitrary branches bypass the path guard; update the if expression in the workflow to remove or replace the broad startsWith('ci/fix-feat-') exemption and instead allow only explicit, known CI fix branch names or a constrained pattern (e.g., exact branch names or a tightly scoped prefix such as 'ci/fix-feat-deps' or a regex whitelist), ensuring the change is applied where the if condition is evaluated (the line containing startsWith(github.head_ref, 'ci/fix-feat-')) so only intended branches can bypass the restricted-path enforcement.

KooshaPari · 2026-02-26T06:57:41Z

[HELIOS-CODEX] Retro-versioned and grouped.

version stamp: \
effective semantic version: \
package: \
layer: \
stack lane: \
branch scope: \

This PR is aligned for stacked/layered merge in the HELIOS-CODEX run and should merge after any earlier wave dependency and before any later-wave dependency.

KooshaPari · 2026-02-26T06:58:32Z

[HELIOS-CODEX] Retro-versioned and grouped.\n\n- version stamp: HELIOS-CODEX/v6.8.87-0-codex0.101.0\n- effective semantic version: v6.8.87-0+codex0.101.0\n- package: pkg:he:service-runtime\n- layer: HELIOS-CODEX-L0\n- stack lane: Wave A (foundation)\n- branch scope: feat/cliproxy-service-runtime-worktree\n- change package: service runtime\n\nThis PR is aligned for stacked/layered merge in the HELIOS-CODEX run and should merge after any earlier wave dependency and before any later-wave dependency.

KooshaPari · 2026-02-26T07:08:52Z

[HELIOS-CODEX] Versioning rule corrected.\n\nUse this pattern from now on: <project_version>-<codex_minor>.<codex_patch>.\n\n- project version: 0.1.3\n- codex version: 0.123.1\n- corrected composite version: 0.1.3-${codex_version#0.}

KooshaPari · 2026-02-26T07:09:21Z

HELIOS-CODEX versioning correction

Use the corrected composite rule:

If Codex version is 0.123.1 and project version is 0.1.3, final version is 0.1.3-123.1.
Rule: project_version + '-' + codex_major.patch where codex_major.patch is 123.1 from 0.123.1 (drop the leading 0. from codex).

Please keep prior HELIOS notes but normalize package/version fields to this format in labels, release notes, and future comments.

KooshaPari · 2026-02-26T15:10:14Z

@coderabbitai full review

coderabbitai · 2026-02-26T15:10:23Z

✅ Actions performed

Full review triggered.

ci: align required check names and allow ci/fix-feat translator diffs

5d1fddb

KooshaPari mentioned this pull request Feb 26, 2026

feat: add cross-platform service management helper #421

Closed

coderabbitai bot reviewed Feb 26, 2026

View reviewed changes

KooshaPari added HELIOS-CODEX Bundle identifier for HELIOS-CODEX release train HELIOS-CODEX-L0 HELIOS-CODEX foundation layer pkg:he:service-runtime HELIOS-CODEX service runtime package labels Feb 26, 2026

KooshaPari merged commit b03bf01 into feat/cliproxy-service-runtime-worktree Feb 27, 2026
9 checks passed

KooshaPari deleted the ci/fix-feat-cliproxy-service-runtime-worktree branch February 27, 2026 09:24

This was referenced Mar 12, 2026

ci: make go-ci test output visible in logs #860

Merged

[CI] Snyk Security failing on main #862

Closed

coderabbitai bot mentioned this pull request Mar 15, 2026

[CI] Fortify AST Scan failing on main #863

Closed

Conversation

KooshaPari commented Feb 26, 2026 • edited by coderabbitai bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

gemini-code-assist bot commented Feb 26, 2026

Uh oh!

coderabbitai bot commented Feb 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Rate limit exceeded

Walkthrough

Changes

Estimated code review effort

Poem

Uh oh!

KooshaPari commented Feb 26, 2026

Uh oh!

coderabbitai bot commented Feb 26, 2026

Uh oh!

coderabbitai bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Feb 26, 2026

Choose a reason for hiding this comment

Uh oh!

KooshaPari commented Feb 26, 2026

Uh oh!

KooshaPari commented Feb 26, 2026

Uh oh!

KooshaPari commented Feb 26, 2026

Uh oh!

KooshaPari commented Feb 26, 2026

HELIOS-CODEX versioning correction

Uh oh!

KooshaPari commented Feb 26, 2026

Uh oh!

coderabbitai bot commented Feb 26, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

KooshaPari commented Feb 26, 2026 •

edited by coderabbitai bot

Loading

coderabbitai bot commented Feb 26, 2026 •

edited

Loading