Add dotbot act + label-gated dotbot review GitHub Actions workflows
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Summary
Port the dotbot code act and dotbot code review GitHub Actions workflows from the ovh-k8s-cluster repo into dotCMS/core.
Background
The OVH cluster repo runs AI-powered automation via the pinned wezell/openrouter-code-review-action:
- dotbot-act — responds to
/dotbot ...comments on PRs with autonomous edits (act mode) - dotbot-review — runs an autonomous AI code review on PRs (review mode)
For core, the review should not run on every PR (cost/noise) — it should only run when a PR is explicitly labeled PR : dotbot review.
Requirements
-
dotbot-act.ymlworkflow copied verbatim — fires on/dotbotcomments on PRs (issue + review comments), excludes dependabot -
dotbot-review.ymlworkflow gated on thePR : dotbot reviewlabel — runs only on labeled PRs, re-runs on subsequent pushes (synchronize) to that PR - Review fires immediately when the label is applied (include
labeled/unlabeledtrigger types; concurrency + cancel-in-progress handles label removal) - Label expression quoted in YAML (label name contains
:, invalid in a plain scalar) -
PR : dotbot reviewlabel created on the repo
Repo prerequisites (settings, not code)
-
OPENROUTER_API_KEYsecret set in repo secrets (does not carry over from ovh-k8s-cluster) - Optional:
DOTBOT_REVIEW_MODELSrepo variable to override default review models
Implementation
PR: #37162
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the dotbot-act and dotbot-review workflows in the ovh-k8s-cluster repository, then inspect PR #37162 and the corresponding .github/workflows changes in dotCMS/core. Done means both workflows meet the listed trigger, label, exclusion, and concurrency requirements, and the PR label is created; repository secrets and variables remain prerequisites.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100