You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@sverka/compiler-github package: pure function compileGithubWorkflow(plan, config?) that compiles a canonical Sverka Plan IR to a GitHub Actions workflow YAML string
Thin wrapper per ADR-004: single job runs sverka execute .sverka/plan.json
Maps plan credentials (CredentialDeclaration.envVar) to job-level env: block with ${{ secrets.VAR }} references
camelCase → kebab-case conversion for permissions (securityEvents → security-events) and triggers (pullRequest → pull_request, workflowDispatch → workflow_dispatch)
Deterministic output: same plan + config → identical YAML
No custom errors (pure function on validated Plan; native Error propagates)
Adds @sverka/compiler-github, a pure compileGithubWorkflow(plan, config?) that compiles a Sverka Plan into a deterministic GitHub Actions workflow. Generates one job that checks out, sets up Node 24 and Bun, installs Sverka, runs sverka execute, and uploads .sverka/output/ artifacts.
New Features
Single job: actions/checkout@v4, actions/setup-node@v4 (Node "24"), oven-sh/setup-bun@v2, bun install -g sverka@<version>, sverka execute, upload .sverka/output/ via actions/upload-artifact@v4 (if: always()).
Credentials → job env: with ${{ secrets.VAR }} (deduped); omits env: when none.
Correct kebab-case conversion (no leading hyphen); restrict id-token to "write".
Removed the .sverka/plan.json arg from sverka execute; added explicit Bun setup via oven-sh/setup-bun@v2.
Written for commit 095dc11. Summary will update on new commits.
CodeAnt-AI Description
Generate configurable GitHub Actions workflows from Sverka plans
What Changed
Added a public compiler that turns a Sverka plan into a deterministic GitHub Actions workflow YAML string
Generated workflows check out the repository, set up Node and Bun, install the selected Sverka version, run sverka execute, and upload output artifacts even when execution fails
Added configurable workflow names, runners, tool versions, triggers, and GitHub permissions, with defaults for common CI use
Declared plan credentials are exposed through GitHub Secrets in a deduplicated job-level environment block
Added coverage for default and custom workflows, triggers, credentials, permissions, deterministic output, empty plans, and the public API
Impact
✅ Faster setup for GitHub Actions workflows ✅ Credentials available from GitHub Secrets ✅ Artifacts preserved after failed checks
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
@codeant-ai ask: Your question here
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
@codeant-ai ask: Can you suggest a safer alternative to storing this secret?
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
@codeant-ai: Your feedback here
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
@codeant-ai: Do not flag unused imports.
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
@codeant-ai: review
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.
Generated workflows include checkout, setup, installation, execution, and artifact upload steps.
Provides deterministic output and sensible defaults, including support for plans with no operations.
Documentation
Added implementation and specification documentation for the GitHub compiler.
Tests
Added coverage for configuration, credentials, permissions, defaults, determinism, and public API behavior.
Walkthrough
The PR defines a synchronous GitHub workflow compiler, adds its public types and exports, implements deterministic YAML generation from Plan data, maps credentials to GitHub secrets, and adds package configuration and Vitest coverage.
Changes
GitHub workflow compilation
Layer / File(s)
Summary
Compiler scope and public contract engdocs/architecture/wave-12-compiler-github-plan.md, specs/12-compiler-github/spec.md
The specification and implementation plan define a synchronous thin-wrapper API, supported configuration, credential mapping, deterministic serialization, excluded features, and verification gates.
Compiler implementation and package wiring packages/compiler-github/src/types.ts, packages/compiler-github/src/compile.ts, packages/compiler-github/src/index.ts, packages/compiler-github/package.json, packages/compiler-github/project.json
The package adds typed configuration, workflow generation, trigger and permission conversion, credential secret mapping, execution steps, artifact upload, YAML serialization, public exports, dependencies, and updated package commands.
Fixtures and compiler validation packages/compiler-github/src/__tests__/*
Vitest coverage verifies defaults, custom settings, triggers, credentials, permissions, deterministic output, empty plans, fixtures, and public runtime exports.
Generated credential mappings are not usable by operations: the SDK supplies empty credentials and the host executor forwards only its PATH allowlist, so GitHub secret environment variables are dropped before checks run. This concrete security/correctness issue needs human review, and no CI ran for the non-trivial change.
The reason will be displayed to describe this comment to others. Learn more.
Review Summary
This PR introduces the @sverka/compiler-github package that compiles Sverka Plan IR to GitHub Actions workflows. I've identified critical logic errors that prevent the code from functioning correctly and must be fixed before merge.
Critical Issues Found (4)
toKebab() function creates invalid output - Produces leading hyphens for capitalized strings (e.g., "Contents" → "-contents"), which will generate malformed GitHub Actions YAML
buildTriggers() silently drops user push configurations - Creates push trigger structure but never assigns to result object
buildTriggers() silently drops user pullRequest configurations - Creates pull_request trigger structure but never assigns to result object
Test validates incorrect YAML escaping - Tests expect escaped ${{ }} syntax that GitHub Actions cannot parse, masking the string escaping bug in buildCredentialEnv()
All issues have specific fixes provided. Please address these before merging.
You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.
• Introduces a pure Plan→GitHub Actions YAML compiler using a thin-wrapper workflow (ADR-004).
• Maps Plan credential envVars to job-level env secrets and normalizes trigger/permission keys.
• Adds comprehensive vitest coverage and updates package scaffolding + spec/docs for v1 scope.
Diagram
graph TD
A["Plan IR (validated)"] --> B["compileGithubWorkflow()"] --> C["workflow object"] --> D["YAML stringify"] --> E["workflow.yml string"]
F["GithubCompilerConfig"] --> B
B --> G["GitHub Actions"]
subgraph Legend
direction LR
_data["Input/Output"] ~~~ _fn["Pure function"] ~~~ _ext["External system"]
end
Loading
High-Level Assessment
The following are alternative approaches to this PR:
1. Template-based YAML emission (string builder)
➕ Absolute control over emitted YAML shape/formatting (e.g., null vs empty map).
➕ Avoids YAML library dependency and any surprising serializer behaviors.
➖ Harder to evolve safely (indentation/escaping/key-order bugs).
➖ More manual effort to keep deterministic and valid across edge cases.
➖ Contradicts ADR-004/thin-wrapper scope; significantly higher complexity and maintenance.
➖ Requires additional mapping decisions (SARIF, artifacts per op, permissions).
Recommendation: Keep the current thin-wrapper + yaml stringify approach: it matches ADR-004, stays small/pure, and the included tests cover key contract points (defaults, config overrides, triggers, permissions, credentials, determinism). If formatting control ever becomes a pain point, prefer adding schema-aligned types over switching to manual string templates.
• Builds deterministic workflow YAML via yaml.stringify with defaults for name/runner/versions, converts camelCase→kebab-case for permissions and trigger keys, and maps unique Plan credential envVars to job env secrets.
package.jsonFix exports to .mjs/.d.mts and declare runtime deps+9/-5
Fix exports to .mjs/.d.mts and declare runtime deps
• Switches main/module/types/exports to ESM .mjs and .d.mts outputs and adds @sverka/ir + yaml as dependencies with standard build/test/lint/typecheck scripts.
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
The PR introduces the @sverka/compiler-github package. While the implementation aligns with the architectural intent of ADR-004, the Codacy analysis indicates the code is not up to standards with 164 new issues.
There are several critical issues that should prevent merging:
Broken Workflow Permissions: The current logic for custom permissions will unintentionally disable the default contents: read permission, causing repository checkout to fail.
Environment Incompatibility: The workflow targets the ubuntu-latest runner but relies on bun, which is not pre-installed, leading to inevitable CI failures.
Maintainability Risks: The core compilation logic in compile.ts has been flagged for high cyclomatic complexity and lacks unit test coverage, posing a long-term stability risk.
About this PR
The PR has introduced 164 new quality issues according to Codacy. Please review the linting and style guidelines for the workspace to ensure the new package meets the project's quality standards.
Test suggestions
Default configuration produces expected workflow structure, steps, and default triggers (push on main, pull_request)
Custom configuration overrides defaults for name, runner, sverka version, and node version
Trigger mapping correctly handles custom branch lists and workflow_dispatch toggle
Credential declarations from multiple operations are collected, deduplicated, and mapped to the env block
Permission mapping correctly converts camelCase keys to kebab-case (e.g., security-events)
Empty operations list results in a valid workflow that still executes the plan
The compiler output is identical when given the same plan and configuration inputs
Public API correctly exports the compiler function and necessary types without exposing internal logic
Automate unit tests for compile.ts to address coverage gaps in complex logic
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Automate unit tests for compile.ts to address coverage gaps in complex logic
buildTriggers() can return an empty on: mapping when config.on is provided but no events are
enabled (e.g. {}), producing a workflow that never triggers. It also emits push.branches: [] for
push: [], which matches no branches and is inconsistent with the empty-array behavior used for
pullRequest.
The new implementation constructs a trigger object by conditionally adding keys; when none match, it
returns {}. It also directly spreads triggers.push into branches even when the array is empty,
which creates a branch filter that matches no branches.
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution
### Issue description
`buildTriggers()` returns `{}` for an explicitly-provided but empty `config.on` object, yielding a workflow with no effective triggers. It also treats `push: []` as enabled and generates `branches: []`, which matches nothing and is likely not what callers intend.
### Issue Context
This behavior is introduced in the new GitHub compiler and affects generated workflows.
### Fix Focus Areas
- packages/compiler-github/src/compile.ts[20-41]
### Implementation notes
Choose one explicit policy and implement it consistently:
- If `config.on` is provided but results in no enabled events, throw an `Error` (with a clear message), OR fall back to the default triggers.
- Treat `push: []` consistently with `pullRequest: []`:
- either interpret empty arrays as “all branches” (emit `push: null` / omit `branches`),
- or reject empty arrays as invalid configuration.
- Add/adjust unit tests to cover `{ on: {} }` and `{ on: { push: [] } }`.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
2. Bun not installed✓ Resolved🐞 Bug☼ Reliability
Description
The generated workflow runs bun install -g sverka@... but never installs or sets up Bun, so the
output is not self-contained and will fail on runners where Bun isn’t preinstalled. Add a Bun setup
step or switch to an install method that only requires Node.
The emitted steps include Node setup and then immediately call bun install, with no prior Bun
installation step. GitHub provides a dedicated action to install Bun in workflows, indicating Bun
setup is normally explicit.
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution
### Issue description
The compiled workflow invokes `bun install` but the steps only set up Node. This makes the generated workflow dependent on the runner image having Bun already installed.
### Issue Context
The compiler currently emits:
- `actions/setup-node@v4`
- then `bun install -g ...`
with no Bun setup.
### Fix Focus Areas
- packages/compiler-github/src/compile.ts[95-110]
### Implementation notes
Pick one:
1) Add Bun setup:
- Insert `- uses: oven-sh/setup-bun@v2` (optionally configurable version) before the `bun install` command.
2) Avoid Bun dependency:
- Replace `bun install -g sverka@...` with `npm install -g sverka@...` (or `corepack`-based approach) so only Node is required.
Update tests to assert the presence of the chosen setup/install mechanism.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
buildCredentialEnv() interpolates CredentialDeclaration.envVar directly into `${{
secrets.<ENV_VAR> }}, but Plan validation only requires envVar` to be a non-empty string. This
allows validated Plans to generate invalid GitHub secret references and/or invalid env keys when
envVar doesn’t meet GitHub secret naming rules.
+ for (const envVar of envVars) {+ env[envVar] = `\${{ secrets.${envVar} }}`;+ }
Evidence
The compiler constructs secret references using dot-notation from envVar without sanitization,
while the IR validator only checks envVar is non-empty. GitHub documents stricter constraints on
secret names, so some validated Plans can still produce invalid workflows.
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution
### Issue description
`buildCredentialEnv()` uses `envVar` verbatim both as an `env:` key and in `secrets.<envVar>` expression form. The IR validator currently only checks `envVar` is non-empty, so invalid names can pass validation and still produce workflows that GitHub cannot resolve correctly.
### Issue Context
- `@sverka/ir` validation rule for `credentials[].envVar` is only “non-empty string”.
- GitHub restricts secret names to alphanumeric/underscore and forbids starting with a number or `GITHUB_`.
### Fix Focus Areas
- packages/compiler-github/src/compile.ts[63-75]
- packages/ir/src/validate.ts[303-325]
### Implementation notes
Prefer rejecting invalid input over silently renaming:
- Add a validation step (either in the compiler or in `@sverka/ir` `validatePlan`) that enforces GitHub secret naming constraints for `CredentialDeclaration.envVar` when targeting GitHub.
- Suggested check: `^[A-Za-z_][A-Za-z0-9_]*$` and not starting with `GITHUB_`.
- If invalid, throw `Error` (compiler) or return a validation error (IR), so callers don’t ship a broken workflow.
- Add a unit test demonstrating that an invalid `envVar` is rejected.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
Review mode: ⚖️ Balanced: Downgraded extended -> standard: change is below the extended eligibility bar (hunks 15/18, lines 1050/200; both must reach the floor). Router rationale: This introduces a new runtime compiler with YAML generation, trigger/permission/credential mappings, public API and package integration across many independent edit sites, creating a dense set of subtle contract and workflow-validity defects that benefit from redundant review.
Tip of the day
💡 Did you know, you can group findings by type and pick your Finding display, from Minimal to Full
GitHub Actions supports "write" and "none" for id-token, but not "read". Align the specification with the public type by removing "read".
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@specs/12-compiler-github/spec.md` around lines 59 - 65, Update the
GithubPermissions.idToken property type to allow only "write", removing "read"
while leaving the other permission properties unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@engdocs/architecture/wave-12-compiler-github-plan.md`:
- Around line 73-83: Specify the `text` language on the fenced file-tree code
block in the architecture plan by changing its opening fence, while leaving the
tree content unchanged.
In `@packages/compiler-github/src/__tests__/compile.test.ts`:
- Around line 48-57: Update the workflow trigger test around the pullRequest
configuration to use a non-default branch such as "release" instead of "main",
and assert that the generated pull_request trigger includes "release". Preserve
the existing assertions for workflow_dispatch and the other configured branch.
- Around line 130-135: Update the empty-plan test in the “compileGithubWorkflow
— empty operations” suite to parse the generated yaml before asserting it.
Validate the parsed workflow structure, including the required jobs entry and
sverka execute command, rather than relying only on substring checks.
In `@specs/12-compiler-github/spec.md`:
- Around line 9-11: The v1 GitHub workflow specification currently invokes the
unsupported plan-file form of the CLI. Update the documented workflow, ADR-004,
architecture plan, and related tests to invoke `sverka execute` without
`.sverka/plan.json`, preserving SDK config loading or auto-discovery and the
single-job wrapper behavior.
---
Outside diff comments:
In `@specs/12-compiler-github/spec.md`:
- Around line 59-65: Update the GithubPermissions.idToken property type to allow
only "write", removing "read" while leaving the other permission properties
unchanged.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
Push a commit to this branch (recommended)
Create a new PR with the fixes
ℹ️ Review info⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 3ab74e1b-5658-4c87-90a9-4588802e5971
📥 Commits
Reviewing files that changed from the base of the PR and between a1026a5 and da5a17b.
[uncategorized] ~49-~49: The official name of this software platform is spelled with a capital “H”.
Context: ...DK uses temp dir for artifacts). The github/codeql-action/upload-sarif@v3 step ...
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 7
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@engdocs/architecture/wave-12-compiler-github-plan.md`:
- Line 388: Remove the hardcoded /home/pepl/projects/sverka directory change
from the verification block and replace it with a checkout-independent root
transition using cd ../.. after the package-level commands or git rev-parse
--show-toplevel.
- Line 166: Update the documented command examples and acceptance criteria at
the referenced architecture-plan sections and in the compiler GitHub
specification to use `sverka execute` without the `.sverka/plan.json` argument,
matching the compiler and package tests.
- Around line 253-256: Update the YAML test around the parsed workflow output to
assert the structured values at on.push.branches, on.pull_request.branches, and
on.workflow_dispatch rather than relying only on string containment. Explicitly
map pullRequest to pull_request and workflowDispatch to workflow_dispatch when
building or reading the expected trigger structure; do not use generic
camelCase-to-kebab-case conversion.
- Around line 289-302: Update the GithubPermissions definition to add optional
idToken with only the "write" value, and update buildPermissions to emit it as
the kebab-case YAML key id-token. Preserve the existing camelCase-to-kebab-case
mapping and reject or avoid supporting idToken: "read".
In `@packages/compiler-github/src/__tests__/compile.test.ts`:
- Around line 114-121: Update the permissions tests around compileGithubWorkflow
so the default workflow permissions are parsed and explicitly verified not to
include id-token. Preserve the existing custom-permission assertion for
securityEvents kebab-case conversion, while ensuring the default-permission
coverage rejects id-token: write.
- Around line 64-111: Update the credential tests around compileGithubWorkflow
to parse the serialized workflow and assert the expected mappings are located
specifically at jobs.sverka.env. Replace substring-based checks in the
declared-credentials test with an exact environment-object assertion, and in the
deduplication test assert jobs.sverka.env contains exactly one TOKEN key.
- Around line 7-28: Update the tests around compileGithubWorkflow to parse the
generated YAML and assert workflow fields at their required paths: jobs.sverka
for runner, tool versions, and steps/actions; on for default triggers; and
permissions for contents access. Apply the same structured assertions to the
default and custom workflow cases, while retaining validation that each
generated document is valid YAML.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
Push a commit to this branch (recommended)
Create a new PR with the fixes
ℹ️ Review info⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: f47e49bf-b2e5-4907-8d02-3b79e0bd9f4a
📥 Commits
Reviewing files that changed from the base of the PR and between da5a17b and 04ddc86.
[uncategorized] ~49-~49: The official name of this software platform is spelled with a capital “H”.
Context: ...DK uses temp dir for artifacts). The github/codeql-action/upload-sarif@v3 step ...
Pure function compileGithubWorkflow(plan, config?) that compiles a canonical
Sverka Plan to a GitHub Actions workflow YAML string. Thin wrapper per
ADR-004: single job runs `sverka execute .sverka/plan.json`. Maps plan
credentials to job-level env block with ${{ secrets.VAR }} references.
camelCase→kebab-case conversion for permissions and triggers. Deterministic
output. No custom errors (pure function on validated Plan). 13 tests pass.
Generated with [Devin](https://devin.ai)
Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
- Mark file-tree fence as in architecture plan
- Test pullRequest trigger with a non-default branch and parse the YAML
- Parse empty-plan YAML output and assert required workflow structure
Co-Authored-By: Petr Plenkov <petr.plenkov@gmail.com>
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
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.
codeant-ai
Bot
added
the
size:XL
![amazon-q-developer[bot]](https://avatars.githubusercontent.com/in/1220912?s=60&v=4){kind=small}
![codeant-ai[bot]](https://avatars.githubusercontent.com/in/646884?s=60&v=4){kind=small}
![codacy-production[bot]](https://avatars.githubusercontent.com/in/56611?s=60&v=4){kind=small}
![qodo-code-review[bot]](https://avatars.githubusercontent.com/in/484649?s=60&v=4){kind=small}
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
baz-reviewer
Bot
added
baz: needs review
baz: pending
and removed
baz: pending
baz: needs review
labels
User description
Summary
@sverka/compiler-githubpackage: pure functioncompileGithubWorkflow(plan, config?)that compiles a canonical Sverka Plan IR to a GitHub Actions workflow YAML stringsverka execute .sverka/plan.jsonCredentialDeclaration.envVar) to job-levelenv:block with${{ secrets.VAR }}referencessecurityEvents→security-events) and triggers (pullRequest→pull_request,workflowDispatch→workflow_dispatch)Errorpropagates)Stack:
main→ #1 → #2 → #3 → #5 → #6 → #7 → #8 → #9 → #10 → #11 → #13 (wave-11-checks) → this PRTest plan
anytypes in implementationGenerated with Devin
Summary by cubic
Adds
@sverka/compiler-github, a purecompileGithubWorkflow(plan, config?)that compiles a Sverka Plan into a deterministic GitHub Actions workflow. Generates one job that checks out, sets up Node 24 and Bun, installs Sverka, runssverka execute, and uploads.sverka/output/artifacts.New Features
actions/checkout@v4,actions/setup-node@v4(Node "24"),oven-sh/setup-bun@v2,bun install -g sverka@<version>,sverka execute, upload.sverka/output/viaactions/upload-artifact@v4(if: always()).env:with${{ secrets.VAR }}(deduped); omitsenv:when none.ubuntu-latest,permissions: { contents: "read" }, triggerspush: [main]+pull_request; optionalworkflow_dispatch.Bug Fixes
id-tokento"write"..sverka/plan.jsonarg fromsverka execute; added explicit Bun setup viaoven-sh/setup-bun@v2.Written for commit 095dc11. Summary will update on new commits.
CodeAnt-AI Description
Generate configurable GitHub Actions workflows from Sverka plans
What Changed
sverka execute, and upload output artifacts even when execution failsImpact
✅ Faster setup for GitHub Actions workflows✅ Credentials available from GitHub Secrets✅ Artifacts preserved after failed checks🔄 Retrigger CodeAnt AI Review
💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.