Add workflow Gen pr

[WSQS]

Summary by CodeRabbit

• Chores
  • Added a manual GitHub Actions workflow to generate pull requests via an AI-assisted process, with secure token and external API support.
  • Introduced a configuration for high-reliability PR generation: configurable AI model and reasoning effort, extra generation options, verbose logging, and a project test command for validation.

[coderabbitai]

Walkthrough

Adds a manually-triggered GitHub Actions workflow to generate PRs from issues and a configuration file for the PR-generation AI, specifying models, tooling, extra args, verbosity, and a test command.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow \.github/workflows/gen-pr.yml	New workflow "Generate PR with AI" (manual trigger) defining job gen-pr on ubuntu-latest with permissions for contents and pull-requests (write) and issues (read); injects GITHUB_TOKEN and OPENROUTER_API_KEY; steps: checkout and run WillBooster/gen-pr action with model args, extra model arguments, and verbose logging.
PR Generation Configuration gen-pr.config.yml	New declarative config for AI PR generation: planning-model set to openrouter/openrouter/polaris-alpha, reasoning-effort: high, repomix-extra-args including compression, remove-empty-lines, include .cpp and .ixx; coding-tool: aider with aider-extra-args aligned to Polaris model; verbose: true; test-command: "cmake -S . -B build".

Sequence Diagram(s)

sequenceDiagram
    autonumber
    participant User as Developer (manual trigger)
    participant GH as GitHub Actions
    participant Repo as Repository (checkout)
    participant Action as gen-pr Action
    participant AI as OpenRouter / Model API
    Note over GH,Action: Environment: GITHUB_TOKEN, OPENROUTER_API_KEY
    User->>GH: Manually trigger "Generate PR with AI"
    GH->>Repo: checkout repository
    GH->>Action: invoke WillBooster/gen-pr with config
    Action->>AI: send planning-model & extra args (polaris-alpha, repomix args, aider args)
    AI-->>Action: return plan / patch
    Action->>GH: create PR (uses GITHUB_TOKEN)
    GH-->>User: PR created / notification

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• New files only, declarative configuration and standard workflow steps.
• Review attention suggestions:
  • Verify secrets usage and minimal permissions in .github/workflows/gen-pr.yml.
  • Confirm repomix-extra-args and aider-extra-args values match intended behavior.
  • Validate test-command correctness for the repository build system.

Poem

🐇 I hopped to the repo with keys in my paw,
A workflow to summon the AI with awe.
Polaris and aider in neat little rows,
A PR blooms where the rabbit nose goes.
✨🧩

Pre-merge checks and finishing touches

✅ 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 'Add workflow Gen pr' accurately describes the main change: adding a GitHub Actions workflow for PR generation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch gen-pr

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1fef06d and c369039.

📒 Files selected for processing (1)

• gen-pr.config.yml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• gen-pr.config.yml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (13)

• GitHub Check: build (Release, gcc)
• GitHub Check: build (windows-latest, Debug, gcc)
• GitHub Check: build (windows-latest, Debug, clang)
• GitHub Check: build (windows-latest, Release, gcc)
• GitHub Check: build (windows-latest, Release, clang)
• GitHub Check: build (windows-latest, Release, cl)
• GitHub Check: build (windows-latest, Debug, cl)
• GitHub Check: build (windows-latest, Debug, clang)
• GitHub Check: build (Release, clang)
• GitHub Check: build (Debug, clang)
• GitHub Check: build (Release, gcc)
• GitHub Check: build (windows-latest, Debug, gcc)
• GitHub Check: build (Debug, gcc)

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[deepsource-io]

Here's the code health analysis summary for commits c06b349..c369039. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
C & C++	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (3)

.github/workflows/gen-pr.yml (1)

28-33: Model specification is duplicated between workflow and configuration.

Line 32 passes --model openrouter/openrouter/polaris-alpha to aider-extra-args, while gen-pr.config.yml (line 8) also specifies the same model. This duplication could lead to inconsistency if one is updated without the other. Consider relying solely on the config file and removing the redundant argument here, or document why both are needed.

Consider this simplified approach:

      - name: Generate PR from issue using OpenRouter
        uses: WillBooster/gen-pr@v4.1.4
        with:
          issue-number: ${{ inputs.issue-number }}
-         aider-extra-args: "--model openrouter/openrouter/polaris-alpha"
          verbose: true

gen-pr.config.yml (2)

2-2: Align model specification strategy across workflow and config.

The planning-model (line 2) and aider-extra-args (line 8) both specify openrouter/openrouter/polaris-alpha, which duplicates the model passed via workflow argument (.github/workflows/gen-pr.yml line 32). Establish a single source of truth: either rely entirely on configuration here or remove it from the config and pass it only via the workflow.

Also applies to: 8-8

---

11-12: Consider the applicability and generality of project-specific settings.

The test-command cmake -S . -B build is specific to C++ projects using CMake. If this config is shared across repositories or used in environments where CMake is not available, this could cause failures. Either document when this config applies, parameterize the test command, or ensure all repos using this workflow are C++ CMake-based projects.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c06b349 and 1fef06d.

📒 Files selected for processing (2)

• .github/workflows/gen-pr.yml (1 hunks)
• gen-pr.config.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (11)

• GitHub Check: build (windows-latest, Release, cl)
• GitHub Check: build (windows-latest, Release, clang)
• GitHub Check: build (windows-latest, Debug, cl)
• GitHub Check: build (windows-latest, Debug, gcc)
• GitHub Check: build (windows-latest, Release, gcc)
• GitHub Check: build (windows-latest, Debug, clang)
• GitHub Check: clang-tidy-review
• GitHub Check: build (Release, clang)
• GitHub Check: build (Debug, clang)
• GitHub Check: build (Release, gcc)
• GitHub Check: build (Debug, gcc)

🔇 Additional comments (1)

.github/workflows/gen-pr.yml (1)

1-33: Verify the OPENROUTER_API_KEY secret is configured and documented.

The workflow requires secrets.OPENROUTER_API_KEY to be defined in repository settings, but there's no documentation or validation that it exists. Consider adding a comment or documentation on how to set up this secret.

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"