[TASK] Phase 3: Configuration and Initial Deployment
Open
Nobody has claimed this yet.
dotCMS : Build
stale
Team : Enablement
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Description
Configure the auto-remediation system and deploy to merge queue workflow:
- Set repository variables and secrets
- Configure opt-in for merge queue only (initial rollout)
- Deploy and test with real merge queue failures
- Monitor diagnostic accuracy
This is Phase 3 of the Auto-Remediation EPIC (#34656).
Acceptance Criteria
- ANTHROPIC_API_KEY secret configured
- Repository variables set: AUTO_REMEDIATION_ENABLED=true, AUTO_REMEDIATION_WORKFLOWS="-2 Merge Group Check", AUTO_CREATE_ISSUES=true
- SLACK_REPORT_CHANNEL configured
- Workflow deployed to main branch
- Test with actual merge queue failure
- Verify diagnostic completes within 10 minutes
- Verify issue created with correct template and labels
- Verify Slack notification sent with diagnosis
- Monitor for 1 week and collect metrics
Priority
High
Additional Context
Configuration Steps:
- Add ANTHROPIC_API_KEY secret (Settings → Secrets → Actions)
- Set repository variables via gh CLI or UI
- Deploy workflow files to main
- Test with triggered merge queue failure
Depends on: Phase 1 (#34657), Phase 2 (issue TBD)
Related: Parent EPIC #34656
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 with the workflow files from Phases 1 and 2, then review Settings → Secrets → Actions and the repository variables configured through the gh CLI or UI. Done means the merge-queue workflow is deployed to main, a real failure completes diagnosis within 10 minutes, and the issue, labels, Slack notification, and one-week metrics meet the listed criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100