The CLI currently outputs something like:
Changed Packages:
o foobar
o zipquux
o helloworld
Unchanged Packages:
o boombam
o whackadoo
Sometimes I want to do multiple changesets immediately after eachother, so on first cycle, I'd do:
Changed Packages:
o foobar
x zipquux
x helloworld
Unchanged Packages:
o boombam
o whackadoo
(ie; write my changeset for zipquux & helloworld packages)
Now I have some unstaged changes:
- .changesets
- a-set
- changes.md
- changes.json
Now, I want to do a changeset for the foobar package, and end up seeing the same UI again:
Changed Packages:
o foobar
o zipquux
o helloworld
Unchanged Packages:
o boombam
o whackadoo
But ideally I'd prefer if changesets scans unstaged changes in .changesets and groups out packages with changesets just added:
No Changsets:
o foobar
Uncommited Changeset:
o zipquux
o helloworld
Unchanged Packages:
o boombam
o whackadoo
Which makes it really easy for me to see that I only have foobar remaining to write a changeset for.
The CLI currently outputs something like:
Sometimes I want to do multiple changesets immediately after eachother, so on first cycle, I'd do:
(ie; write my changeset for
zipquux&helloworldpackages)Now I have some unstaged changes:
Now, I want to do a changeset for the
foobarpackage, and end up seeing the same UI again:But ideally I'd prefer if
changesetsscans unstaged changes in.changesetsand groups out packages with changesets just added:Which makes it really easy for me to see that I only have
foobarremaining to write a changeset for.