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
then it should show a list of commits that have taken place between HEAD and the given package's previous release (going off of the Git tags). This command should be a proxy over git log, so the user should be able to pass arbitrary arguments to this command they would usually be able to pass to git log.
then it should show a commits with changes that have taken place between HEAD and the given package's previous release (going off of the Git tags). This command should be a proxy over git diff, so the user should be able to pass arbitrary arguments to this command they would usually be able to pass to git log.
(I realize that it may be strange to pass commands to a tool that supposedly creates a release branch, but I'm considering renaming this tool to indicate that it can be used to manage releases and not just create them. That's a different ticket, though.)
The text was updated successfully, but these errors were encountered:
If the user runs this command from within a monorepo:
then it should show a list of commits that have taken place between HEAD and the given package's previous release (going off of the Git tags). This command should be a proxy over
git log
, so the user should be able to pass arbitrary arguments to this command they would usually be able to pass togit log
.Similarly, if the user runs
then it should show a commits with changes that have taken place between HEAD and the given package's previous release (going off of the Git tags). This command should be a proxy over
git diff
, so the user should be able to pass arbitrary arguments to this command they would usually be able to pass togit log
.(I realize that it may be strange to pass commands to a tool that supposedly creates a release branch, but I'm considering renaming this tool to indicate that it can be used to manage releases and not just create them. That's a different ticket, though.)
The text was updated successfully, but these errors were encountered: