build constantly fails with "stdin: is not a tty"

[alex-rusakevich]

stdin: is not a tty is not a serious problem, but why scp-action rollbacks and fails the whole build because of it? Can I make scp-action ignore this?

github actions log:

tar all files into /tmp/NKJYOrGgWZ.tar.gz
scp file to server.
create folder /home/***/releases
drone-scp error:  stdin: is not a tty

drone-scp rollback: remove all target tmp file
remove file NKJYOrGgWZ.tar.gz
2023/08/*** 14:57:40 stdin: is not a tty

[lamemakes]

I'm also seeing this - would be curious if you found a fix. Thanks!

[lamemakes]

It looks like ssh-action is unaffected by this as well. Not sure if there's something that should be done on the server side to surpress this. Behavior can be seen here: https://github.com/lamemakes/lame-site/actions/runs/6011922542/job/16309445119 (replace old assets -> ssh-action, deploy assets -> scp-action)