Skip to content

Commit e01b52f

Browse files
docs(daily-ops): remove redundant sections to reduce bloat (#28658)
1 parent aa39e6a commit e01b52f

1 file changed

Lines changed: 0 additions & 15 deletions

File tree

docs/src/content/docs/patterns/daily-ops.md

Lines changed: 0 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -7,13 +7,6 @@ sidebar:
77

88
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.
99

10-
## When to Use DailyOps
11-
12-
- **Continuous improvement** - Daily code quality improvements
13-
- **Progressive migrations** - Gradually update dependencies or patterns
14-
- **Documentation maintenance** - Keep docs fresh with daily updates
15-
- **Technical debt** - Chip away at issues one small PR at a time
16-
1710
## The DailyOps Pattern
1811

1912
### Scheduled Execution
@@ -84,14 +77,6 @@ This repository implements several DailyOps workflows demonstrating different us
8477

8578
All follow the phased approach with discussions for tracking and draft pull requests for review.
8679

87-
## Implementation Guide
88-
89-
1. **Define Goal** - Identify ongoing goal (test coverage, performance, docs sync)
90-
2. **Design Workflow** - Set weekday schedule, configure `safe-outputs` for discussions/PRs
91-
3. **Research Phase** - Analyze state, create discussion, wait for approval
92-
4. **Config Phase** - Create config files, test, submit PR, wait for approval
93-
5. **Execute Daily** - Make small improvements, verify, create draft PRs, update discussion
94-
9580
## Related Patterns
9681

9782
- **IssueOps** - Trigger workflows from issue creation or comments

0 commit comments

Comments
 (0)