Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

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

storybookjs / storybook Public

Notifications You must be signed in to change notification settings
Fork 9.4k
Star 85.8k

Code
Issues 2k
Pull requests 134
Discussions
Actions
Projects 2
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Security
Insights

Release tooling: Release stable releases from `latest-release` v2#24380

Closed

JReinhold wants to merge 4 commits intonextstorybookjs/storybook:nextfrom release-stable-to-lateststorybookjs/storybook:release-stable-to-latestCopy head branch name to clipboard

+9-7

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Oct 5, 2023

fix prerelease -> non-patch naming
JReinhold
committed
improve merge conflict hnadling between next and latest-release
JReinhold
committed
make merge conflict handling more resilient
JReinhold
committed
fix merging commit message
JReinhold
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.