Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci(editor): Write custom github action for generating changelog from PR names and throw out the changeset package #4171

Conversation

CodingDive
Copy link
Contributor

@CodingDive CodingDive commented Oct 9, 2024

Split it into two actions. One that does the automated changelog based on branch names (we can still change it manually), runs on every branch. And the existing github action that publishes it to npm and pushes the tag as a release to Github. This one only runs on staging

…PR names and throw out the changeset package
Copy link

vercel bot commented Oct 9, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
frontend ✅ Ready (Inspect) Visit Preview Oct 11, 2024 8:05am

Copy link
Contributor

github-actions bot commented Oct 9, 2024

📦 Next.js Bundle Analysis for @serlo/frontend

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

Mikey Stengel added 3 commits October 9, 2024 18:50
…te-custom-github-action-auto-generating-release-notes' into chore/delete-change-sets-and-write-custom-github-action-auto-generating-release-notes
.github/workflows/editor.yaml Outdated Show resolved Hide resolved
@CodingDive CodingDive merged commit f4a6c51 into staging Oct 11, 2024
9 checks passed
@CodingDive CodingDive deleted the chore/delete-change-sets-and-write-custom-github-action-auto-generating-release-notes branch October 11, 2024 10:53
@github-actions github-actions bot mentioned this pull request Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants