ci: Configure auto-merge for monthly reports workflow#589
Merged
Conversation
Replace direct push to main with PR-based workflow that enables auto-merge. This improves security by respecting branch protection rules and provides an audit trail for automated reports. Changes: - Update permissions: pull-requests read → write - Create feature branch: monthly-report/YYYY-MM - Commit changes to feature branch - Push branch and create PR with gh CLI - Enable auto-merge with gh pr merge --auto --merge The PR will automatically merge after status checks pass and merge queue clears, respecting all repository protection rules. Implementation follows Option A from .planning/research/automerge-workflow-research.md
Update ROADMAP.md to reflect completed status: - Changed milestone status from 'In Progress' to 'COMPLETE' - Updated milestone description (biweekly → monthly, project board → repositories) - Marked Phase 2 as complete with deliverables verified - Added research document from auto-merge investigation All phases delivered: - Phase 1: Automated Report System ✅ - Phase 2: Navigation & Discovery ✅ - Phase 3: Documentation & Refinement ✅ v1.1 milestone is production-ready.
castrojo
added
github_actions
kind/automation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Configures the monthly-reports workflow to create PRs with auto-merge enabled instead of pushing directly to main.
Changes
File Modified:
.github/workflows/monthly-reports.ymlKey Updates:
pull-requests: read→pull-requests: writepermissionmonthly-report/YYYY-MMgh pr merge --auto --mergeBenefits
✅ Security Improvement: Respects branch protection rules (no bypass)
✅ Audit Trail: PRs provide reviewable record of automated changes
✅ Quality Gates: Merge queue ensures status checks pass before merge
✅ Rollback Capability: PRs can be closed/reverted if issues detected
✅ Governance Compliance: Follows repository's pull request workflow
How It Works
Research
Based on comprehensive research documented in
.planning/research/automerge-workflow-research.mdOption A selected: Native
gh pr merge --autoapproachTesting
Manual trigger command:
```bash
gh workflow run monthly-reports.yml
```
Next automated run: First Monday of next month
Related
.planning/research/automerge-workflow-research.md