You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 23, 2021. It is now read-only.
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:
yarn in repo and call getReleasePlan() using { sinceMaster: true }
With the output - check the length of the 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).
If there are, format the data in releasesin some way to display this information.
Open questions:
a) is this mad?
b) how do we format the info?
i) probably need to separate packages from dependents here
ii) a table maybe?
iii) Do we include any summary info or leave that for PR-inspection?
Major downside:
requires this doing a yarn install etc