Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

documentation for doing a release manually #312

Open
basisbit opened this issue Sep 2, 2021 · 1 comment
Open

documentation for doing a release manually #312

basisbit opened this issue Sep 2, 2021 · 1 comment

Comments

@basisbit
Copy link

basisbit commented Sep 2, 2021

There are various common reasons why the plugin might fail, without it giving a helpful error message or how to continue. Thus, imho it would be very helpful to add some documentation in the README.md file on what which step does and what commands are needed to manually run it. Then users can copy & pasta them into shell after resolving a merge conflict or a faulty version number update or various other things.

@aleksandr-m
Copy link
Owner

It doesn't make sense to add this to the readme. Goal steps depend on the configuration. It would be great to have continue feature or at least print out commands to the console in case of failure, but it is not a trivial task to do so. Ideas / PR-s are welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants