You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
echo "::warning::AMPLIFY_DOCS_WEBHOOK_URL secret not set — docs-archive branch was updated, but the live site stays stale until the next main build. Create an Amplify incoming webhook (docs app → Build settings → Incoming webhooks) and store its URL in this secret."
239
+
exit 0
240
+
fi
241
+
# The archive force-push above already succeeded, so a flaky
242
+
# webhook must not fail the workflow. Bound the request (timeout
243
+
# + retries) and downgrade any failure to a warning — the live
-X POST "$WEBHOOK" -H 'Content-Type: application/json' -d '{}'; then
247
+
echo "Amplify rebuild triggered."
248
+
else
249
+
echo "::warning::Amplify webhook POST failed after retries — the docs-archive branch is already updated, so the live site will refresh on the next main build. Re-run this workflow (or POST the webhook manually) to force it sooner."
Copy file name to clipboardExpand all lines: .github/workflows/storybook-coverage-checker.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ You are a Storybook coverage analyzer. When a PR is ready for review, analyze ch
44
44
45
45
### Step 1: Find the PR
46
46
47
-
Use the GitHub MCP server tools (configured via `tools.github.toolsets: [pull_requests, repos]`) to find the pull request for the current branch. Query open pull requests whose head ref matches the current branch name and select the most recent one.
47
+
Use the GitHub MCP server tools (configured via `tools.github.toolsets: [pull_requests, repos]`) to find the pull request for the current branch. Query open pull requests whose head ref matches the current branch name and select the most recent one.**Remember this PR number** — because this workflow runs via `workflow_dispatch` (no triggering PR context), you must pass it explicitly as `item_number` when you call `add_comment` (see Important Notes below).
48
48
49
49
### Step 2: Get Changed Component Files
50
50
@@ -139,7 +139,7 @@ loading: {
139
139
-`-propName`: Removed prop (in story, not in component)
140
140
-`~propName`: Changed prop (type mismatch)
141
141
4.**BAI-specific props**: Focus on props defined in the component's own interface, not inherited from Ant Design
142
-
5.**Use `add_comment`**: This safe-output tool will automatically comment on the relevant pull request when configured with `target: "*"`, so `item_number`is not required
142
+
5.**Use `add_comment`**: Because `safe-outputs.add-comment` is configured with `target: "*"` (this workflow is dispatched, so it has no triggering PR), you **must** set `item_number`in the `add_comment` output to the pull request number you identified in Step 1. Omitting it makes the safe-output handler fail with "no specific item number was provided".
0 commit comments