Thanks, but both are actually different processes. You can check my post on automatic deployments using Github actiona via heroku here : dev.to/aishikamidder05/deploy-reac...
Yes, I read that post, I actually commented on it :D. Could you please explain how are the two processes different? Or more importantly, how is the end result different? I have some apps connected to the Heroku this way and each time I push changes to GitHub, it gets automatically redeployed on Heroku.
Oh, I'm so sorry, got confused. I got a notif on my other post. In the other one, I've utilized a library and used actions to send me notifications automatically via twilio and mailgun.
Here, I've done same like you explained. I've just automated the deployment process using github actions. So, when I make a commit, it gets updated on it's own.
Thanks, but both are actually different processes. You can check my post on automatic deployments using Github actiona via heroku here : dev.to/aishikamidder05/deploy-reac...
Yes, I read that post, I actually commented on it :D. Could you please explain how are the two processes different? Or more importantly, how is the end result different? I have some apps connected to the Heroku this way and each time I push changes to GitHub, it gets automatically redeployed on Heroku.
Oh, I'm so sorry, got confused. I got a notif on my other post. In the other one, I've utilized a library and used actions to send me notifications automatically via twilio and mailgun.
Here, I've done same like you explained. I've just automated the deployment process using github actions. So, when I make a commit, it gets updated on it's own.
Heroku charges you to automatically run tests. With GitHub Actions, you can automate unit tests for free and host to Heroku for free.