@laiboonh I’m with you on this - out of nowhere last week we noticed a “fun” error message using github actions with gigalixir (all documented in this issue on gigalixir-cli). They’ve since extended the ssh options to allow for -tt which works fine from dev local but was still failing with a 255 status exit when run as part of the github actions pipeline.
Here is my fork that does show the -tt option during migrate.
After the change above^ I don’t get the error Pseudo-terminal will not be allocated because stdin is not a terminal but the journey doesn’t end there. Next I found that my public key was denied (interesting given this was never a problem before last week).
Running migrations root@v2018-us-central1.gcp.ssh.gigalixir.com: Permission denied (publickey). Command '['ssh', '-tt', 'root@v2018-us-central1.gcp.ssh.gigalixir.com', '-p', '31266', 'gigalixir_run', 'migrate']' returned non-zero exit status 255.
To get around this problem I generated a new ssh key like so
ssh-keygen -t ed25519 -C "email@here.com"
Next, copy the private key and create a new secret for Github Actions named SSH_PRIVATE_KEY
pbcopy < id_ed23456
Finally, from your local machine add the public key to gigalixir
gigalixir account:ssh_keys:add "$(cat ~/.ssh/id_ed23456.pub)"
And now when you kick this deploy using github actions it’s running migrations without issue. Big thanks to @mhanberg and I’ve opened an issue on the main github project for others to benefit