We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi Rasso! Thanks for this Tool!
Before uploading the files from a local folder, checking that there are no unpushed changes in the current working directory would be nice to have.
This can prevent some accidental mistakes where uncomitted files are deployed to the server via rsync.
The text was updated successfully, but these errors were encountered:
Great idea! I think it would make sense to still allow deployment with an unclean working dir. But asking "Are you sure?" would be nice.
Aside from that, checking if the latest local commit matches the latest remote commit (if there is a remote) could also proof handy.
Sorry, something went wrong.
Personally I would prefer separate action for doing this. It's a more conscious decision then.
No branches or pull requests
Hi Rasso! Thanks for this Tool!
Before uploading the files from a local folder, checking that there are no unpushed changes in the current working directory would be nice to have.
This can prevent some accidental mistakes where uncomitted files are deployed to the server via rsync.
The text was updated successfully, but these errors were encountered: