From 8bd9e01ca32d84635e32cc2d441210b88ca8790c Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Mon, 27 Apr 2026 04:28:31 +0000 Subject: [PATCH] docs(daily-ops): remove redundant sections to reduce bloat MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Removed two sections whose content was already covered elsewhere: - "When to Use DailyOps": duplicated intro paragraph and workflow examples list - "Implementation Guide": duplicated the "Phased Approach" section Result: 103 → 88 lines (-15%), 23 → 14 list items (-39%). Co-Authored-By: Claude Sonnet 4.6 --- docs/src/content/docs/patterns/daily-ops.md | 15 --------------- 1 file changed, 15 deletions(-) diff --git a/docs/src/content/docs/patterns/daily-ops.md b/docs/src/content/docs/patterns/daily-ops.md index b26bc0ff74d..513f0fb5360 100644 --- a/docs/src/content/docs/patterns/daily-ops.md +++ b/docs/src/content/docs/patterns/daily-ops.md @@ -7,13 +7,6 @@ sidebar: DailyOps workflows automate incremental progress toward large goals through small, scheduled daily changes. Work happens automatically in manageable pieces that are easy to review and integrate. -## When to Use DailyOps - -- **Continuous improvement** - Daily code quality improvements -- **Progressive migrations** - Gradually update dependencies or patterns -- **Documentation maintenance** - Keep docs fresh with daily updates -- **Technical debt** - Chip away at issues one small PR at a time - ## The DailyOps Pattern ### Scheduled Execution @@ -84,14 +77,6 @@ This repository implements several DailyOps workflows demonstrating different us All follow the phased approach with discussions for tracking and draft pull requests for review. -## Implementation Guide - -1. **Define Goal** - Identify ongoing goal (test coverage, performance, docs sync) -2. **Design Workflow** - Set weekday schedule, configure `safe-outputs` for discussions/PRs -3. **Research Phase** - Analyze state, create discussion, wait for approval -4. **Config Phase** - Create config files, test, submit PR, wait for approval -5. **Execute Daily** - Make small improvements, verify, create draft PRs, update discussion - ## Related Patterns - **IssueOps** - Trigger workflows from issue creation or comments