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

Add check changeset workflow #179

Merged
merged 4 commits into from
May 15, 2024
Merged

Add check changeset workflow #179

merged 4 commits into from
May 15, 2024

Conversation

khiga8
Copy link
Contributor

@khiga8 khiga8 commented May 15, 2024

This PR introduces a workflow to ensure that every PR has a changeset and/or the skip changeset label.

Context: I forgot to add a changeset in a PR earlier, and scrambled to add it in a follow-up. Having this check in place will be helpful since it's easy to forget.

I copied the check changeset workflow over from Primer React!

Copy link

changeset-bot bot commented May 15, 2024

⚠️ No Changeset found

Latest commit: d2ab13c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@khiga8 khiga8 marked this pull request as ready for review May 15, 2024 15:50
@khiga8 khiga8 requested a review from a team as a code owner May 15, 2024 15:50
@khiga8 khiga8 requested a review from jonrohan May 15, 2024 15:50
@khiga8 khiga8 merged commit 04c0abb into main May 15, 2024
8 checks passed
@khiga8 khiga8 deleted the kh-add-check-changeset-workflow branch May 15, 2024 16:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants