-
Notifications
You must be signed in to change notification settings - Fork 592
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
Update README.md #4393
Update README.md #4393
Conversation
We want to make our template more discoverable. - [💬 Internal Slack thread](https://github.slack.com/archives/C02NUUQ9C30/p1710415630143979)
🦋 Changeset detectedLatest commit: 2dc9dcb The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
size-limit report 📦
|
@@ -0,0 +1,5 @@ | |||
--- | |||
"@primer/react": patch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We usually release the docs changes without a changeset but did you want to announce this in the release notes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That was my plan. I was getting a warning though because there wasn't a changeset?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah the CI job will fail if there is no changeset. You could either add a changeset like you did here or you can add skip changeset
label.
Co-authored-by: Owen Niblock <owenniblock@github.com>
We wanted to make our template more discoverable to avoid that internal employees have to set up their own project and run into unexpected issues.