Merge pull request #1 from lightspeedwp/copilot/fix-e67c9b25-708b-464… by ashleyshaw · Pull Request #2 · lightspeedwp/.github

ashleyshaw · 2025-09-17T13:23:36Z

…e-a0ca-0719d5ffef8a

Add GitHub Copilot MCP configuration with Playwright and GitHub remote servers

…e-a0ca-0719d5ffef8a Add GitHub Copilot MCP configuration with Playwright and GitHub remote servers

coderabbitai · 2025-09-17T13:23:44Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests

Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch master

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Implements all critical release automation components to fix blocking issues. ## Changes ### Release Agent (✅ Implemented) - Implement `.github/agents/release.agent.cjs` - Complete release automation - Validates VERSION and CHANGELOG.md - Bumps semantic versions (major/minor/patch) - Updates changelog with release date - Creates git tags - Publishes GitHub releases - Supports dry-run mode for testing - Handles both GitHub Actions and standalone execution ### Validation Scripts (✅ Implemented) - Implement `scripts/validate-version.cjs` - Semantic version validation - Validates VERSION file format - Parses version components (major.minor.patch[-prerelease][+build]) - Comprehensive error reporting - Implement `scripts/validate-changelog.cjs` - Changelog validation - Validates Keep a Changelog format - Checks version and date formats - Validates section structure - Reports detailed errors ### Utilities (✅ Implemented) - Implement `.github/agents/includes/changelogUtils.cjs` - Changelog parser - Parses Keep a Changelog format - Validates changelog structure - Extracts releases and sections - CLI tool with --validate, --parse, --latest, --unreleased modes ### Schemas (✅ Created) - Create `automation/schemas/changelog.schema.json` - Changelog validation - Create `automation/schemas/version.schema.json` - Version validation - Create `automation/schemas/frontmatter.schema.json` - Frontmatter validation ### Workflow Updates (✅ Updated) - Update `.github/workflows/release.yml` - Enable release agent - Update `.github/workflows/release-prep.yml` - Fix script references - Update `.github/workflows/changelog.yml` - Enable validation, add Node setup ## Issues Resolved - ✅ Critical Issue #1: Release agent not implemented (was placeholder) - ✅ Critical Issue #2: validate-changelog.js was placeholder (exit code 1) - ✅ Critical Issue #3: validate-version.js was empty - ✅ Critical Issue #4: changelogUtils.js missing - ✅ Critical Issue #5: Schema files missing ## Testing All components tested and working: - ✅ validate-version.cjs validates current VERSION file - ✅ validate-changelog.cjs validates current CHANGELOG.md - ✅ changelogUtils.cjs parses and validates changelog - ✅ release.agent.cjs runs successfully in dry-run mode ## Notes - All scripts renamed from .js to .cjs for CommonJS compatibility - Package.json contains "type": "module", so .cjs extension required - Release agent supports --scope=major|minor|patch and --dry-run flags - Follows LightSpeed coding standards and documentation requirements Refs: G-1, G-2 (release agent and changelog utils implementation)

Completes the remaining medium-priority items from the release agent review. Adds PR automation, Release Notes Manager agent, and comprehensive scope parameter documentation. ## Changes ### 1. PR Automation for release-prep.yml (✅ Complete) **Created: `scripts/create-release-pr.cjs`** - Automatically creates release PRs from develop to main - Computes next version based on merged PR labels - Updates VERSION and CHANGELOG.md files - Creates release branch (release/vX.Y.Z) - Generates comprehensive PR description with: - Changelog summary - Release checklist - Version bump information - Uses gh CLI for PR creation **Updated: `.github/workflows/release-prep.yml`** - Added "Create Release PR" step - Calls create-release-pr.cjs script - Passes GITHUB_TOKEN for authentication - Removes TODO comment (now implemented) **Features:** - Validates unreleased changes exist before creating PR - Detects if release branch already exists - Computes semantic version bumps (major/minor/patch) - Commits and pushes changes automatically - Comprehensive error handling and logging ### 2. Release Notes Manager Agent (✅ Complete) **Created: `.github/agents/release-notes-manager.agent.cjs`** Comprehensive release notes generation agent that: - Compiles clean release notes from changelog - Generates highlights from key sections (Added, Changed, Security) - Detects and flags breaking changes automatically - Lists contributors with PR counts - Groups changes by type with emojis (✨ Added, 🐛 Fixed, etc.) - Formats output suitable for GitHub releases - Includes installation instructions - Links to full changelog comparison **CLI Usage:** ```bash # Generate notes for specific version node .github/agents/release-notes-manager.agent.cjs --version=1.0.0 # Generate notes for latest version node .github/agents/release-notes-manager.agent.cjs --latest # Output to file node .github/agents/release-notes-manager.agent.cjs --version=1.0.0 --output=RELEASE_NOTES.md ``` **Features:** - ✅ Highlights (top 5 important changes) - ✅ Breaking changes detection and warnings - ✅ Grouped sections with emojis - ✅ Contributor attribution - ✅ Installation instructions - ✅ Full changelog links - ✅ Graceful error handling for missing tags **Implements spec:** `.github/agents/TODO/release-notes-manager.agents.md` ### 3. Scope Parameter Documentation (✅ Complete) **Created: `docs/RELEASE-SCOPE-GUIDE.md`** Comprehensive 400+ line guide covering: **Overview:** - What the --scope parameter does - Semantic versioning primer - How it affects version bumping **Detailed Sections:** - When to use each scope (patch/minor/major) - Real-world examples for each scope type - Decision flowchart for scope selection - Release label system integration **Examples:** - Bug fix release (patch) - New feature release (minor) - Breaking change release (major) - Dry-run testing examples **Best Practices:** - Validation before release - Documentation requirements - Testing procedures - Communication guidelines **FAQ:** - Common questions and answers - Edge cases and troubleshooting - Pre-release versions - Reverting releases - Monorepo considerations **Related Documentation:** - Links to release process guide - Agent specifications - External SemVer reference - Support channels ## Testing All components tested and working: ✅ **create-release-pr.cjs** - Script executes without errors - Validates unreleased changes - Handles missing tags gracefully ✅ **release-notes-manager.agent.cjs** - Generates comprehensive release notes for 0.1.0 - Handles missing git tags gracefully - Formats output with proper markdown - Includes highlights, breaking changes, grouped sections - Lists contributors (when available) ✅ **RELEASE-SCOPE-GUIDE.md** - Well-structured and comprehensive - Clear examples and use cases - Proper YAML frontmatter - Links to related documentation ## Benefits 1. **Automated PR Creation** - Reduces manual work for maintainers - Ensures consistent PR format - Validates changelog before PR creation - Integrates with existing workflows 2. **Professional Release Notes** - User-friendly format - Highlights key changes - Warns about breaking changes - Credits contributors 3. **Clear Documentation** - Removes ambiguity about version bumping - Provides decision framework - Real-world examples - Answers common questions ## Standards Compliance - ✅ UK English throughout - ✅ LightSpeed coding standards - ✅ Comprehensive JSDoc comments - ✅ YAML frontmatter in documentation - ✅ Error handling and logging - ✅ CommonJS compatibility (.cjs extension) ## Related Issues - Addresses medium-priority item #1: PR automation - Addresses medium-priority item #2: Release Notes Manager - Addresses medium-priority item #3: Scope documentation - Completes TODO in release-prep.yml (line 25) ## Next Steps The release automation is now feature-complete for MVP: - ✅ All critical issues resolved - ✅ All medium-priority items completed - ⏳ Low-priority polish items remain (optional) --- **Dependencies:** Requires .cjs scripts from previous commit **Breaking Changes:** None **Migration Required:** None

- Add missing file_type, owners, tags to audit documents - Fix Issue #1.1 implementation to convert planner.agent.js to ES6 (not reviewer to CommonJS) - Fix Issue #2.3 parameter naming: files → filenames for clarity - Fix Issue #2.4 function reference: hasChangelog → hasChangelogEntry Addressed code review feedback from Gemini Code Assist: - Repository uses 'type: module' in package.json - Parameter naming must reflect actual data type - Function references must be consistent across issues https://claude.ai/code/session_01LfLtQ4tii1MMDS9Vggn5vh

…s — resolve CHANGELOG conflict (#2)

…D-002 #1548) ## Changes ### 1. Updated .github/workflows/release.yml - Added release job outputs: release_version, release_branch - Added post-release-sync job to sync main → develop after release - Documented develop-first flow in workflow comments ### 2. Created scripts/workflows/release/post-release-sync.cjs - Automates sync of main changes back to develop after release - Creates chore/post-release-sync-main-to-develop branch - Merges main into develop to keep branches synchronized - Creates PR for developer review/merge ### 3. Rewrote docs/RELEASE_PROCESS.md - Complete rewrite for develop-first flow (v3.0.0) - Added ASCII flow diagram - Documented authorization gating (new in v3.0) - Detailed stacked PR workflow (PR #1 to develop, PR #2 to main) - Added post-release sync process - Updated pre-release checklist ### 4. Enhanced docs/BRANCHING_STRATEGY.md - Expanded section 7 Release Flow with detailed subsections - Added 7.1 Release Flow (develop-first stacked PRs) - Added architectural diagram - Documented authorization gating requirements - Added 7.2 Hotfix Flow (urgent production fixes) Closes#1548 Related: #1546, #1547 Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

* fix: Implement authorization gating for release workflow (CHILD-001 #1547) ## Changes ### 1. Remove continue-on-error flag from trigger-telemetry job - Removed `continue-on-error: true` from .github/workflows/release.yml - Now authorization failures will properly block downstream jobs ### 2. Enhanced authorization validation in trigger-telemetry.cjs - Added input validation for GITHUB_ACTOR and GITHUB_EVENT_NAME - Added authFailureReason tracking throughout validation logic - Improved logging with clearer success/failure messages - Enhanced telemetry JSON payload with failure_reason field - Better error handling for missing GITHUB_TOKEN ### 3. Comprehensive test suite (trigger-telemetry.test.cjs) - Tests for authorized maintainer team members - Tests for unauthorized users - Tests for invalid trigger events - Tests for API errors and missing inputs - Tests for telemetry recording and process exit codes ## Result ✅ Authorization gating now properly blocks unauthorized releases ✅ Audit logging captures all authorization attempts and failures ✅ Workflow fails immediately if authorization fails (no workaround) Closes#1547 Related: #1546 (Epic) Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com> * refactor: Implement develop-first release flow with stacked PRs (CHILD-002 #1548) ## Changes ### 1. Updated .github/workflows/release.yml - Added release job outputs: release_version, release_branch - Added post-release-sync job to sync main → develop after release - Documented develop-first flow in workflow comments ### 2. Created scripts/workflows/release/post-release-sync.cjs - Automates sync of main changes back to develop after release - Creates chore/post-release-sync-main-to-develop branch - Merges main into develop to keep branches synchronized - Creates PR for developer review/merge ### 3. Rewrote docs/RELEASE_PROCESS.md - Complete rewrite for develop-first flow (v3.0.0) - Added ASCII flow diagram - Documented authorization gating (new in v3.0) - Detailed stacked PR workflow (PR #1 to develop, PR #2 to main) - Added post-release sync process - Updated pre-release checklist ### 4. Enhanced docs/BRANCHING_STRATEGY.md - Expanded section 7 Release Flow with detailed subsections - Added 7.1 Release Flow (develop-first stacked PRs) - Added architectural diagram - Documented authorization gating requirements - Added 7.2 Hotfix Flow (urgent production fixes) Closes#1548 Related: #1546, #1547 Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com> * docs: Remove broken workflow badges and add text-based status (CHILD-003 #1549) ## Changes ### Removed broken badges from BRANCHING_STRATEGY.md - Deleted 33-line badge block (BADGES-START to BADGES-END) - These badges linked to non-existent GitHub Actions workflow status pages - Replaced with text-based status indicator: 'Status: This document describes policies...' - Added link to workflows directory for actual workflow status ## Result ✅ Removed broken 404 badge links from documentation ✅ Added text-based alternative (more reliable than badges) ✅ Documentation validates without broken link errors ✅ Lint checks pass Closes#1549 Related: #1546, #1547, #1548 Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Haiku 4.5 <noreply@anthropic.com>

- Fix#1: Positional mode validation — reject unsupported modes like 'typo' - Fix#2: Days input validation — reject NaN, non-integer, and non-positive values - Fix#3: Script validation — reject unknown scripts and mode-incompatible selections - Fix#4: Output file reporting — stop claiming output was saved when handlers don't write - Fix#5: Exit status — exit with code 1 when any handler fails - Fix#6: Dry-run consistency — honor --dry-run flag in apply mode (was hardcoded false) - Fix#7: Test quality — replace literal assertions with logic tests for orchestrator behaviour Test coverage expanded from 29 to 33 tests covering all fixes. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

* docs: Add Phase 2 Label Orchestrator changelog entry Added comprehensive changelog entry documenting Phase 2 label-orchestrator CLI implementation, including three operating modes (audit, sync, apply), input validation, mode-specific constraints, dry-run defaults, and test coverage. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com> * feat: Phase 2 - Unified label orchestrator CLI - Add label-orchestrator.js: unified CLI for all label management scripts - Support modes: audit (analyse), sync (synchronise dry-run), apply (live changes) - Unified reporting, progress tracking, and error handling - 29 unit tests for argument parsing, validation, and mode dispatch - Orchestrates manage-stale-issues, review-meta-labels, review-status-labels, sync-pr-labels Resolves#1720 (Create Shared Utilities - Phase 2 expansion) Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com> * fix: Address 7 CodeRabbit review issues in Phase 2 orchestrator - Fix#1: Positional mode validation — reject unsupported modes like 'typo' - Fix#2: Days input validation — reject NaN, non-integer, and non-positive values - Fix#3: Script validation — reject unknown scripts and mode-incompatible selections - Fix#4: Output file reporting — stop claiming output was saved when handlers don't write - Fix#5: Exit status — exit with code 1 when any handler fails - Fix#6: Dry-run consistency — honor --dry-run flag in apply mode (was hardcoded false) - Fix#7: Test quality — replace literal assertions with logic tests for orchestrator behaviour Test coverage expanded from 29 to 33 tests covering all fixes. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com> * fix: Eliminate trivial test conditions from exit status tests - Line 217: Replace always-false condition with direct exitCode = 0 - Line 223: Replace always-true condition with realistic error array Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com> * fix: Use errorCount in success test to eliminate unused variable Restore the ternary condition in the success test to match the error test pattern, making both tests consistent and eliminating the unused errorCount variable. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com> * fix: Remove unused errorCount variable from success test Removed unused errorCount declaration that was causing ESLint warning. The success test now directly asserts exitCode = 0 without intermediate variable. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Haiku 4.5 <noreply@anthropic.com>

…rovements Phase 1: Comprehensive fixes to project-docs-update.sh automation suite Security Fixes: - Fixed sed injection vulnerability (CVE prevention) on lines 92, 161 - Use safe delimiter (|) instead of / for sed patterns - Properly escape special characters in project names using parameter expansion - Prevents injection from project names containing /, &, \, etc. Logic Fixes: - Fixed project detection logic (Issue #2): removed overly restrictive pre-existence checks - Fixed find command filtering (Issue #3): corrected directory traversal for proper project discovery - Fixed return value convention (Issue #5): align with bash standards (0=success, 1=failure) - Fixed stats format consistency (Issue #4): standardized on colon-separated format Quality Improvements: - Added --help/-h support (Issue #6) with comprehensive usage information - Created docs/SCRIPT_USAGE.md (3,500+ lines) covering quick-start, integration, troubleshooting - Enhanced test suite with 4 new edge-case tests: * Special characters in project names (/, &, \) * Return value convention validation * Statistics format consistency * Symlink and permission handling Files Modified: - scripts/automation/project-docs-update.sh: All 7 fixes implemented - scripts/automation/test-project-docs-update.sh: New test coverage added - docs/SCRIPT_USAGE.md: NEW comprehensive documentation - CHANGELOG.md: Phase 1 entry added Test Results: - All special character injection tests passing ✓ - Script help text working correctly ✓ - Return value convention tests passing ✓ - Validation logic working as expected ✓ Addresses: Issue #1862 Relates to: Issue #1720 (Issue Maintenance Scripts) Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

…rovements (#1993) Phase 1: Comprehensive fixes to project-docs-update.sh automation suite Security Fixes: - Fixed sed injection vulnerability (CVE prevention) on lines 92, 161 - Use safe delimiter (|) instead of / for sed patterns - Properly escape special characters in project names using parameter expansion - Prevents injection from project names containing /, &, \, etc. Logic Fixes: - Fixed project detection logic (Issue #2): removed overly restrictive pre-existence checks - Fixed find command filtering (Issue #3): corrected directory traversal for proper project discovery - Fixed return value convention (Issue #5): align with bash standards (0=success, 1=failure) - Fixed stats format consistency (Issue #4): standardized on colon-separated format Quality Improvements: - Added --help/-h support (Issue #6) with comprehensive usage information - Created docs/SCRIPT_USAGE.md (3,500+ lines) covering quick-start, integration, troubleshooting - Enhanced test suite with 4 new edge-case tests: * Special characters in project names (/, &, \) * Return value convention validation * Statistics format consistency * Symlink and permission handling Files Modified: - scripts/automation/project-docs-update.sh: All 7 fixes implemented - scripts/automation/test-project-docs-update.sh: New test coverage added - docs/SCRIPT_USAGE.md: NEW comprehensive documentation - CHANGELOG.md: Phase 1 entry added Test Results: - All special character injection tests passing ✓ - Script help text working correctly ✓ - Return value convention tests passing ✓ - Validation logic working as expected ✓ Addresses: Issue #1862 Relates to: Issue #1720 (Issue Maintenance Scripts) Co-authored-by: Claude Haiku 4.5 <noreply@anthropic.com>

* fix: Project documentation scripts — security, logic, and testing improvements Phase 1: Comprehensive fixes to project-docs-update.sh automation suite Security Fixes: - Fixed sed injection vulnerability (CVE prevention) on lines 92, 161 - Use safe delimiter (|) instead of / for sed patterns - Properly escape special characters in project names using parameter expansion - Prevents injection from project names containing /, &, \, etc. Logic Fixes: - Fixed project detection logic (Issue #2): removed overly restrictive pre-existence checks - Fixed find command filtering (Issue #3): corrected directory traversal for proper project discovery - Fixed return value convention (Issue #5): align with bash standards (0=success, 1=failure) - Fixed stats format consistency (Issue #4): standardized on colon-separated format Quality Improvements: - Added --help/-h support (Issue #6) with comprehensive usage information - Created docs/SCRIPT_USAGE.md (3,500+ lines) covering quick-start, integration, troubleshooting - Enhanced test suite with 4 new edge-case tests: * Special characters in project names (/, &, \) * Return value convention validation * Statistics format consistency * Symlink and permission handling Files Modified: - scripts/automation/project-docs-update.sh: All 7 fixes implemented - scripts/automation/test-project-docs-update.sh: New test coverage added - docs/SCRIPT_USAGE.md: NEW comprehensive documentation - CHANGELOG.md: Phase 1 entry added Test Results: - All special character injection tests passing ✓ - Script help text working correctly ✓ - Return value convention tests passing ✓ - Validation logic working as expected ✓ Addresses: Issue #1862 Relates to: Issue #1720 (Issue Maintenance Scripts) Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com> * docs: Project Maintenance Agent — Phase 1 & 2 Documentation Create comprehensive project documentation for the Project Maintenance Agent initiative: **Files Created:** - README.md (project overview, phases, timelines, deliverables) - PLANNING.md (detailed phase breakdown, requirements, success criteria) - OPENSPEC.md (formal technical specification, API contracts, architecture) **Content Summary:** README.md (11.5 KB): - Project overview and goals - Phase 1 ✅ COMPLETE status (merged PR #1867) - Phase 2 (READY TO START) with 2-week timeline - Phase 3 (PLANNED) for team integration - Architecture overview and design decisions - Risk mitigation and next steps PLANNING.md (16 KB): - Executive summary and scope - Phase 1 completion status with test results - Phase 2 detailed requirements: * Agent specification (multi-provider support) * Three portable skills with interfaces * Provider implementations (Claude, Copilot, OpenAI) * Configuration files and testing strategy - Phase 3 GitHub Actions workflows - Success criteria and risk analysis - Open questions and dependencies OPENSPEC.md (18 KB): - Formal technical specification - Functional requirements (FR-1 through FR-5) - Non-functional requirements (NF-1 through NF-5) - Architecture diagrams and data flows - Complete API specification (input/output contracts) - Operational modes (scheduled, on-demand, integration) - Error handling and recovery strategies - Security specifications and injection prevention - Testing strategy (unit, integration, e2e, provider tests) - Configuration for different project types - Performance requirements and deployment stages - Success criteria and monitoring requirements **Key Features:** - Comprehensive Phase 2 timeline (2 weeks, ~50 hours) - 3 portable skills specification (docs-updater, validator, sync) - Multi-provider support (Claude, Copilot, OpenAI) - Both proactive (nightly audit) and reactive (on-demand) modes - Complete API contracts for integration - Security requirements and injection prevention - >80 code coverage target **Related Work:** - Phase 1 PR: #1867 (merged) - Parent Epic: #1862 - Builds on: scripts/automation/project-docs-update.sh **Project Status:** - ✅ Phase 1: Scripts fixed and tested (merged) - 🔄 Phase 2: Ready to start immediately (this documentation) - 📋 Phase 3: Planned for week 4 Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Haiku 4.5 <noreply@anthropic.com>

…ocumentation) Complete handoff document for Task 2.5 quality & testing phase. Includes: - Integration test suite plan (280-320 LOC, 30+ tests) - Documentation requirements (README, Architecture, Troubleshooting) - Performance validation checklist - Security validation requirements - Coverage expansion targets (95%+ overall) - Implementation timeline (2-3 days) Tasks 2.3 & 2.4 Part 1 complete and committed. Ready for Task 2.5 in next session. Related PRs: Tasks 2.1 & 2.2 merged; PR #2.3 & #2.4 in progress Phase 2 Status: 50% complete (2/4 days) Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

Merge pull request#1from lightspeedwp/copilot/fix-e67c9b25-708b-464…
c26629a
…e-a0ca-0719d5ffef8a Add GitHub Copilot MCP configuration with Playwright and GitHub remote servers

ashleyshaw merged commit 12800b5 into copilot/fix-e67c9b25-708b-464e-a0ca-0719d5ffef8aSep 17, 2025
2 of 4 checks passed

ashleyshaw mentioned this pull request May 31, 2026
[PHASE 1] Move Tests Out of .jest-skip/ and Add Missing Coverage #602
Open
34 tasks

This was referenced Jun 1, 2026
[DOCS] Create PR template router at /pull_request_template.md #712
Closed
[DOCS] Create instructions/pr-templates.instructions.md #713
Closed
[DOCS] Update AGENT.md with canonical template rules #715
Closed
[WORKFLOW] Create PR template validation workflow #717
Closed

ashleyshaw added a commit that referenced this pull request Jul 29, 2026
chore(merge): merge develop into feat/playwright-testing-agent-update…
18d6edf
…s — resolve CHANGELOG conflict (#2)

This was referenced Aug 4, 2026
docs(1461): Issue #1461 Architecture Decision & Phase 2 Planning #1466
Merged
[CHILD-002] Fix Release Flow Architecture #1548
Closed

This was referenced Aug 8, 2026
docs: Phase 3 Part 3 — Update versioning and changelog documentation #1639
Merged
[PHASE-4] Implement Stacked PR Release Workflow (PR #1→develop, PR #2→main) #1640
Open

This was referenced Aug 9, 2026
docs: Phase 5-7 Planning & Documentation for Release Process Redesign #1664
Merged
feat: Phase 1.4 Status Label Audit Script #1727
Merged

ashleyshaw mentioned this pull request Aug 19, 2026
docs: Rewrite release documentation (Phase 7) #2116
Merged
15 tasks

Navigation Menu

Uh oh!

Merge pull request #1 from lightspeedwp/copilot/fix-e67c9b25-708b-464… - #2

Merge pull request #1 from lightspeedwp/copilot/fix-e67c9b25-708b-464…#2
ashleyshaw merged 1 commit into
copilot/fix-e67c9b25-708b-464e-a0ca-0719d5ffef8afrom
master

ashleyshaw commented Sep 17, 2025

Uh oh!

coderabbitaiBot commented Sep 17, 2025

Review skipped

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

ashleyshaw commented Sep 17, 2025

Uh oh!

coderabbitaiBot commented Sep 17, 2025

Review skipped

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant