Define CLI commands and parameters

[Eomm]

We should define the big picture of what we want to do with the tool.

The commands I think could be needed are:

# will process the release
releasify publish

# print out all the info as if I release right now
releasify publish --dry-run

# print out the login of git and npm
releasify whoami

# do what will need for the login process
releasify login

Others?

[mcollina]

releasify draft // shows the release notes

[Eomm]

releasify login [--system=[gihub|npm]] (now I'm not sure this will be useful if we use spawn to run commands)

• login to ${system} (default an array with [github, npm])

releasify whoami

• check auth to systems (github + npm) -> fail if you are not logged in

releasify publish --npm-otp=123456

• check auth to systems (github + npm) -> fail if you are not logged in
• check uncommitted code -> fail if there is
• define the release message + lables
• bump version in function of labels
• output the new version
• npm publish
• git push
• build the release on github
• teardown

releasify draft

• check uncommitted code -> fail if there is
• define the release message + lables
• output the new version
• teardown

Could be ok as first version commands and main steps?

[mcollina]

releasify publish --npm-otp=123456

I don't think we need --npm-otp=123456, we just need to make sure that npm publish asks for it to the user.

[Eomm]

An update:

releasify login

This could become a command to facilitate the creation of tokens (github and/or npm). Not sure it is useful so I would drop it.

releasify whoami

Print the npm login, the git user (git config user.email).
It could be good to view also the owner of GitHub token but the API required the name of the account.. so it is useless unless using the same npm username.. but this logic doesn't seem useful right now.

I don't think we need --npm-otp=123456, we just need to make sure that npm publish asks for it to the user.

This will be the next implementation 👍

[Eomm]

Released the v1