You should go a step further and let the building (and testing) also be done via github actions. I've been doing that for a while now and it feels great knowing all i have to do is push my code (and or/release depending on the repo) for it to spin up, do its thing and deploy it to ftp.
Cool! I looked through your GitHub repos and found one of your yml files - I will take it as a starting point to increase automation of my own workflows - thanks again 😊
Yeah i think all that is missing from that repo is the testing part. Just do a command to test and if it fails it should stop all together. The git hard -reset command is there because i had an issue earlier with the ftp plugin also uploading files i don't want to my FTP. Not sure if that is still needed. No problem and have fun with it!
You should go a step further and let the building (and testing) also be done via github actions. I've been doing that for a while now and it feels great knowing all i have to do is push my code (and or/release depending on the repo) for it to spin up, do its thing and deploy it to ftp.
Of course, this should be the logical next step. Do you also use GitHub actions for that? How do you handle failed tests?
I do use GH actions for that yes. And if a test fails i get notified via email and it will simple stop deploying :)
Cool! I looked through your GitHub repos and found one of your yml files - I will take it as a starting point to increase automation of my own workflows - thanks again 😊
Yeah i think all that is missing from that repo is the testing part. Just do a command to test and if it fails it should stop all together. The git hard -reset command is there because i had an issue earlier with the ftp plugin also uploading files i don't want to my FTP. Not sure if that is still needed. No problem and have fun with it!
Thank you for sharing your workflow 👍🏻