feat(ci): add StackBlitz collection link to PR preview comment#6158
feat(ci): add StackBlitz collection link to PR preview comment#6158
Conversation
Link to the SWC-Team Spectrum Web Components StackBlitz collection in the same automated comment as Azure Storybook previews, with a note that demos use published packages and are not branch-specific. Made-with: Cursor
|
📚 Branch Preview Links🧪 StackBlitzBranch / commit
Curated collection (SWC-Team workspace; published package demos) Story-linked templates (from 2nd-gen
🔍 First Generation Visual Regression Test ResultsWhen a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:
Deployed to Azure Blob Storage: If the changes are expected, update the |
- Scan 2nd-gen Storybook CSF files for parameters.stackblitz.url and list them in the automated PR comment (deduped, sorted by component). - Add StackBlitz fork link to the PR head commit using head.repo.full_name so fork PRs resolve correctly. - Clarify that curated and story template links use published npm packages; Storybook previews remain the branch-accurate UI review. Made-with: Cursor
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| /** | ||
| * Collect `.stories.ts` files under a directory (recursive). |
There was a problem hiding this comment.
🚫 [eslint] <jsdoc/tag-lines> reported by reviewdog 🐶
Expected 1 lines after block description
| /** | |
| * Collect `.stories.ts` files under a directory (recursive). | |
| /** | |
| * Collect `.stories.ts` files under a directory (recursive). | |
| * |
| /** | ||
| * Parse `parameters.stackblitz.url` from a Storybook CSF file (best-effort regex). |
There was a problem hiding this comment.
🚫 [eslint] <jsdoc/tag-lines> reported by reviewdog 🐶
Expected 1 lines after block description
| /** | |
| * Parse `parameters.stackblitz.url` from a Storybook CSF file (best-effort regex). | |
| /** | |
| * Parse `parameters.stackblitz.url` from a Storybook CSF file (best-effort regex). | |
| * |
| /** | ||
| * Derive a short component label from `.../components/<name>/stories/...`. |
There was a problem hiding this comment.
🚫 [eslint] <jsdoc/tag-lines> reported by reviewdog 🐶
Expected 1 lines after block description
| /** | |
| * Derive a short component label from `.../components/<name>/stories/...`. | |
| /** | |
| * Derive a short component label from `.../components/<name>/stories/...`. | |
| * |
1 participant
Link to the SWC-Team Spectrum Web Components StackBlitz collection in the same automated comment as Azure Storybook previews, with a note that demos use published packages and are not branch-specific.
Made-with: Cursor
Description
Motivation and context
Related issue(s)
Screenshots (if appropriate)
Author's checklist
Reviewer's checklist
patch,minor, ormajorfeaturesManual review test cases
Descriptive Test Statement
Descriptive Test Statement
Device review
Accessibility testing checklist
Required: Complete each applicable item and document your testing steps (replace the placeholders with your component-specific instructions).
Keyboard (required — document steps below) — What to test for: Focus order is logical; Tab reaches the component and all interactive descendants; Enter/Space activate where appropriate; arrow keys work for tabs, menus, sliders, etc.; no focus traps; Escape dismisses when applicable; focus indicator is visible.
Screen reader (required — document steps below) — What to test for: Role and name are announced correctly; state changes (e.g. expanded, selected) are announced; labels and relationships are clear; no unnecessary or duplicate announcements.