-
Notifications
You must be signed in to change notification settings - Fork 249
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
If all changesets are empty, the action still creates a PR #205
Comments
Yeah, this makes sense - we should skip creating the PR in such a case. I would happily accept a PR fixing this. |
Fixes changesets#205. Note that this maintains the previous behavior that if there are any changesets (even empty ones), the action does not publish packages.
* Don't create a PR if all changesets are empty Fixes #205. Note that this maintains the previous behavior that if there are any changesets (even empty ones), the action does not publish packages. * Create three-needles-protect.md * Update .changeset/three-needles-protect.md Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
What about cases when changests are empty but dependencies got an update? I’d expect the PR to be up in this scenario. |
@kachkaev I'm not sure exactly what you mean here (wouldn't there need to be some changeset somewhere in order for there to be a release in the PR?) but I definitely could have missed something as a non-expert. |
…#206) * Don't create a PR if all changesets are empty Fixes changesets#205. Note that this maintains the previous behavior that if there are any changesets (even empty ones), the action does not publish packages. * Create three-needles-protect.md * Update .changeset/three-needles-protect.md Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
If the only changesets on the branch are "empty" changesets (like those created with
changeset --empty
, perhaps to make achangeset status
CI check pass), the action will still create a PR with no releases. That seems unnecessary? I think it's reasonable thatchangeset version
won't be a no-op in this case (deleting the changeset files or adding them to the list inpre.json
) but creating a PR seems overkill?The text was updated successfully, but these errors were encountered: