-
Notifications
You must be signed in to change notification settings - Fork 2
Display information about the changesets present #3
Comments
I strongly dislike this and would like to avoid it if possible. Could we bundle get-release-plan? I assume we would have the problem of the action getting out of date but I feel like the versioning parts are stable enough that it won't really be a problem.
I like it as an idea
SGTM
My thoughts are that it should be in a table inside a
IMO, don't include it. |
We can bundle Good thought around avoiding the yarn.
Easy agree on these |
With the release of
@changesets/get-release-plan
we can get richer information about the existence non-existence of changesets: I think it would be good to change how this action works to something like:getReleasePlan()
using{ sinceMaster: true }
changesets
array to see if there are new changesets ('empty' changesets is a feature we know AK wants that we want this to work with).releases
in some wayto display this information.Open questions:
a) is this mad?
b) how do we format the info?
Major downside:
requires this doing a yarn install etc
The text was updated successfully, but these errors were encountered: