XS✔ ◾ feat: Epic Cleanup — cluster YakShaver PBIs into smaller focused epics#760
Open
XS✔ ◾ feat: Epic Cleanup — cluster YakShaver PBIs into smaller focused epics#760
Conversation
Adds a GitHub Agentic Workflow to reorganise three large YakShaver epics: - ✨ YakShaver Agent 2.0 (SSW.YakShaver#2811) - ✨ YakShaver Desktop App (SSW.YakShaver.Desktop#677) - ♻️ Auth Migration (SSW.YakShaver#3494) The workflow clusters open PBIs into smaller, focused sub-epics, all created in SSWConsulting/SSW.YakShaver.Desktop for centralised tracking: - 🔌 MCP Integration / 🏗️ Core Infrastructure (Agent 2.0) - 🐛 Bug Fixes / ✨ Features & UX / 🏗️ Platform & Infrastructure (Desktop) - ♻️ Scope 1: Enterprise Auth / 🌐 Scope 2: Extended Providers (Auth) The workflow uses the GitHub MCP to read issues cross-repo and posts reorganisation summaries on each original epic with CLI commands for completing the sub-issue re-linking. Requires: GH_AW_CROSS_REPO_PAT secret with read/write access to both SSWConsulting/SSW.YakShaver and SSWConsulting/SSW.YakShaver.Desktop. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…ng, all PBIs, progress tracking Key changes from initial draft: - Read ALL sub-issues (open + closed), not just open ones - Cluster PBIs holistically across all three epics; Desktop App + Agent 2.0 PBIs sharing the same theme go into the same new smaller epic - Target 10-20 PBIs per cluster (5-8 total) — coarser, fewer epics - All-closed clusters are acceptable; group by theme not by state - New epic body has a full ✅/🔲 progress table per PBI with source repo - Comment on each original epic shows only relevant new epics + all PBI assignments Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
PR Metrics✔ Thanks for keeping your pull request small.
Metrics computed by PR Metrics. Add it to your Azure DevOps and GitHub PRs! |
github-actions
bot
changed the title
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a GitHub Agentic Workflow to automatically cluster PBIs from three large YakShaver epics into 5–8 smaller, theme-focused epics (created in SSWConsulting/SSW.YakShaver.Desktop) and to post summary comments back on the original epics.
Changes:
- Introduces an editable gh-aw workflow prompt file describing the epic clustering + issue/comment creation process.
- Adds the compiled/locked GitHub Actions workflow generated from the prompt file.
- Updates
.gitattributesto treat*.lock.ymlworkflows as generated and resolve merges withours.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| .github/workflows/epic-cleanup-yakshaver.md | Defines the agent instructions, clustering rules, and output templates for new epics + summary comments. |
| .github/workflows/epic-cleanup-yakshaver.lock.yml | Compiled gh-aw workflow that runs the agent, gates outputs via Safe Outputs, and posts results. |
| .gitattributes | Marks *.lock.yml workflows as generated and sets merge strategy. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 61bddf21de
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Contributor
|
🚀 Pre-release build is available for this PR: |
1. Tool schema alignment — use create_issue (not create-issue); remove unsupported fields issue_type and target-repo from agent instructions; agent only provides title, body, labels 2. 50-link comment limit — replace Markdown links with plain SSWConsulting/org.repo#number cross-references in add_comment template; cross-repo commenting on SSW.YakShaver issues documented as manual step 3. Remove progress table — dropped ✅/🔲 PBI table from new epic body; GitHub sub-issue progress bar covers this natively 4. GH_AW_CROSS_REPO_PAT validation — added pre-agent steps: block that checks for the secret early; if missing, posts a warning comment on Desktop epic #677 via GITHUB_TOKEN then exits 1 (fail fast) 5. ubuntu-slim runner — patch activation and safe_outputs jobs from ubuntu-slim to ubuntu-latest in lock file; add runs-on: ubuntu-latest to frontmatter for agent job Also: add title-prefix [YakShaver 2.0] and target-repo to safe-outputs frontmatter so create_issue calls always land in SSW.YakShaver.Desktop with the correct prefix automatically Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
🚀 Pre-release build is available for this PR: |
- Add bash: true tool so agent can write per-epic comment files to /tmp/gh-aw/comments/ during its run - Step 4 now has agent write comment bodies for SSW.YakShaver epics #2811 and #3494 to files AND call add_comment for #677 - Add post-steps: job that reads the files and posts comments to SSWConsulting/SSW.YakShaver using GH_AW_CROSS_REPO_PAT - Add pre-step to mkdir -p /tmp/gh-aw/comments - post-steps skips gracefully if agent did not write a file - Remove 'manually post summary' note — now fully automated - Patch ubuntu-slim to ubuntu-latest in lock file Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Pins GitHub Actions used by gh-aw compiled workflows to exact commit SHAs to prevent tag-mutable supply chain attacks. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
🚀 Pre-release build is available for this PR: |
- Split '✨ Features & UX' into '✨ Features' and '🎨 UX Improvements' - Merge '♻️ Auth Scope 1' and '🌐 Auth Scope 2' into single '♻️ Auth Migration' cluster Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
🚀 Pre-release build is available for this PR: |
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
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
Adds a GitHub Agentic Workflow (\�pic-cleanup-yakshaver) to reorganise the three oversized YakShaver epics in the Product Backlog.
Closes: N/A (workflow creation PR)
What this workflow does
When triggered via \workflow_dispatch, the AI agent:
Source epics being reorganised
Suggested output clusters (agent validates against real PBI content)
Prerequisites
Add \GH_AW_CROSS_REPO_PAT\ to Settings → Secrets → Actions in \SSWConsulting/SSW.YakShaver.Desktop\ with:
Files