ci: require changeset on pull request

[orionmiz]

Adding the changeset is now mandatory for Pull Requests.

Use changeset add --empty if you want to avoid versioning.

[vercel]

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

Name	Status	Preview	Updated (UTC)
stackflow-docs	✅ Ready (Inspect)	Visit Preview	Jan 2, 2025 9:53am

[changeset-bot]

⚠️ No Changeset found

Latest commit: eec641a

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

[tonyfromundefined]

I think it would be better to separate it from the type-check job. How about creating a new job called changeset?

# as-is
jobs:
  type-check:
    # do typescript type check and changeset ci

# to-be
jobs:
  type-check:
    # do only typescript type check
  changeset:
    # do only changeset ci

[orionmiz]

I think it would be better to separate it from the type-check job. How about creating a new job called changeset?

# as-is
jobs:
  type-check:
    # do typescript type check and changeset ci

# to-be
jobs:
  type-check:
    # do only typescript type check
  changeset:
    # do only changeset ci

That's right. but this might be creating a lot of duplicated steps that are hard to maintain.

Let's move on after #553 merged.

Note: I considered composite action containing shared steps(setup node, cache, yarn install) but post-if for conditional cache save is not supported yet.