GitHub: Update PR template to correct canary release workflow link

[valentinpalkovic]

Closes #

What I did

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli-storybook/src/sandbox-templates.ts

• Make sure this PR contains one of the labels below:

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

Summary by CodeRabbit

• Documentation
  • Updated the pull request template to reference the new publish workflow, including corrected links and CLI invocation.
• Chores
  • Aligned internal workflow references in PR template from canary-release to publish for consistency.
• Notes
  • No user-facing functionality, UI, or behavior changes.

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR updates the PR template to reference publish.yml instead of canary-release-pr.yml for the canary/publish workflow links and gh workflow run command. No other content or logic changes.

Changes

Cohort / File(s)	Summary
PR template reference update \.github/PULL_REQUEST_TEMPLATE.md	Replaced references to canary-release-pr.yml with publish.yml in URLs and gh workflow run command.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Release tooling: Use npm Trusted Publishing for canaries #32621 — Migrates canary release logic into publish.yml and removes canary-release-pr.yml, matching the template’s updated references.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch valentin/update-pull-request-template

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/PULL_REQUEST_TEMPLATE.md (1)

73-73: Improve link text for accessibility.

Replace the generic “here” link text with something descriptive so assistive tech users know the destination.

-_core team members can create a canary release [here](https://github.com/storybookjs/storybook/actions/workflows/publish.yml) or locally with `gh workflow run --repo storybookjs/storybook publish.yml --field pr=<PR_NUMBER>`_
+_core team members can create a canary release via the [Publish workflow](https://github.com/storybookjs/storybook/actions/workflows/publish.yml) or locally with `gh workflow run --repo storybookjs/storybook publish.yml --field pr=<PR_NUMBER>`_

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e679e44 and b44deb9.

📒 Files selected for processing (1)

• .github/PULL_REQUEST_TEMPLATE.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.18.1)

.github/PULL_REQUEST_TEMPLATE.md

73-73: Link text should be descriptive

(MD059, descriptive-link-text)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Danger JS
• GitHub Check: Core Unit Tests, windows-latest

[github-actions]

	Fails
🚫	PR is not labeled with one of: ["ci:normal","ci:merged","ci:daily","ci:docs"]

Generated by 🚫 dangerJS against b44deb9

[nx-cloud]

View your CI Pipeline Execution ↗ for commit b44deb9

Command	Status	Duration	Result
nx run-many -t build --parallel=3	✅ Succeeded	48s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-10-08 09:57:38 UTC