fix: make release workflow resilient to enterprise token restrictions#37
Closed
spboyer wants to merge 3 commits into
Closed
fix: make release workflow resilient to enterprise token restrictions#37spboyer wants to merge 3 commits into
spboyer wants to merge 3 commits into
Conversation
- Created ceremonies.md to outline team meeting structures including Design Review, Code Review, and Retrospective. - Established decisions.md to document key team decisions, including model selection directives and documentation maintenance routing. - Added identity files (now.md, wisdom.md) for tracking current focus areas and team insights. - Logged multiple sessions detailing implementation progress, performance audits, and planning activities. - Introduced routing.md to clarify work assignment processes and issue routing for team members. - Added orchestration-log directory for session logs and .gitkeep files for empty directories.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The Microsoft enterprise blocks GITHUB_TOKEN from creating PRs. The release workflow now handles this gracefully: - Pushes the release branch regardless - Attempts PR creation (best-effort) - Attempts auto-merge if PR was created - Falls back to logging the branch URL for manual PR creation - Updates status check context names to match actual required checks Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Member
Author
|
Closing — this accidentally included the Squad migration. Will reopen with just the release workflow fix. |
spboyer
added a commit
that referenced
this pull request
Mar 3, 2026
E2 sensei engine (#32, #33) shipped but SKILL.md still listed `waza dev` as "coming soon". Updated documentation to reflect implemented features. ## Changes **Help text block** - Added DEV FLAGS section: `--target`, `--max-iterations`, `--auto` - Updated command summary to include `[skill-path]` argument **waza dev command section** - Usage examples for scoring workflows - Compliance levels: Low → Medium → Medium-High → High with progression criteria - Scoring checks: description length (150+ chars, 1024 max), trigger phrases, anti-trigger phrases, routing clarity markers, token budget (500 soft / 5000 hard) **Future features section** - Marked trigger accuracy tests (#36), `--skip-integration` (#37), `--fast` (#38), improvement suggestions engine (#34) as "Coming Soon" ```bash # Score and improve to high compliance waza dev skills/my-skill --target high # Auto-apply without prompts waza dev skills/my-skill --auto --max-iterations 3 ``` Current state: waza skill at High compliance (638 chars, 13 triggers, 3 anti-triggers), 2097 tokens. <!-- START COPILOT ORIGINAL PROMPT --> <details> <summary>Original prompt</summary> > > ---- > > *This section details on the original issue you should resolve* > > <issue_title>[E5] Update SKILL.md with sensei engine features when E2 completes</issue_title> > <issue_description>The waza SKILL.md (#52) was created with `waza dev` listed as 'coming soon'. Once Charles completes E2 (#32-38), update the SKILL.md to: > - Document `waza dev` command usage > - Add compliance scoring examples > - Add trigger accuracy test examples > - Update the help text block > > Blocked on: spboyer/waza#33, spboyer/waza#32</issue_description> > > ## Comments on the Issue (you are @copilot in this section) > > <comments> > <comment_new><author>@spboyer</author><body> > @copilot Please pick up this issue. Here's the scope: > > ## What's ready to document (blockers spboyer/waza#32 and spboyer/waza#33 are closed) > > 1. **`waza dev` command usage** — The sensei dev loop is implemented. Document the command, its flags (`--verbose`, `--target-score`, `--max-iterations`), and a usage example in the SKILL.md. > > 2. **Compliance scoring** — Document how compliance scoring works (the scoring system from spboyer/waza#33 is merged). > > ## What's still 'coming soon' (keep as placeholders) > > - Trigger accuracy tests (#36 — still open) > - `--skip-integration` flag (#37 — still open) > - `--fast` flag (#38 — still open) > - Improvement suggestions engine (#34 — still open) > > ## Files to update > - `skills/waza/SKILL.md` — the main SKILL.md for the waza skill > > Read the existing SKILL.md first, then update the sections that reference `waza dev` as 'coming soon' with actual documentation. Keep the token count reasonable (under 500 tokens for the SKILL.md frontmatter+body).</body></comment_new> > </comments> > </details> <!-- START COPILOT CODING AGENT SUFFIX --> - Fixes spboyer/waza#93 <!-- START COPILOT CODING AGENT TIPS --> --- 💬 We'd love your input! Share your thoughts on Copilot coding agent in our [2 minute survey](https://gh.io/copilot-coding-agent-survey). --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: spboyer <7681382+spboyer@users.noreply.github.com>
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.
The Microsoft enterprise blocks
GITHUB_TOKENfrom creating PRs, causing the release extension job to fail.This makes the PR creation step best-effort:
release/vX.Y.Zbranchubuntu-latest,Lint)The CLI release and azd extension build/pack/publish all succeed regardless — only the final registry sync PR is affected.