Skip to content

Helpful note about status command - #639

Merged
Andarist merged 3 commits into
changesets:mainfrom
brianespinosa:patch-2
Nov 7, 2021
Merged

Helpful note about status command#639
Andarist merged 3 commits into
changesets:mainfrom
brianespinosa:patch-2

Conversation

@brianespinosa

Copy link
Copy Markdown
Contributor

I was trying to use the status command to generate a JSON output file for using in CI to report back on which version items were being published. I kept trying to get the status after the version and publish commands as that seemed like the logical state I would be wanting to get status. Hopefully this note helps someone else.

I was trying to use the `status` command to generate a JSON output file for using in CI to report back on which version items were being published. I kept trying to get the status after the `version` and `publish` commands as that seemed like the logical state I would be wanting to get status. Hopefully this note helps someone else.
@changeset-bot

changeset-bot Bot commented Sep 17, 2021

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 016498e

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

@Andarist
Andarist enabled auto-merge (squash) November 7, 2021 09:49
@Andarist
Andarist merged commit a3628d5 into changesets:main Nov 7, 2021
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.

3 participants