You could set different environment variables for the test job. So the job for testing would use separate infrastructure that is designated for testing the code within a pull request. If the job is successful, you know that the code is working and it is ready to be merged :)
You can create a script that essentially performs the exact same commands that you would run in the command line to deploy your code. There are also packages that you can use in GitHub Actions which will allow you to do deployments, so check if there is one for your hosting provider as it could save you a lot of time! :)
Nice video, but why they make build directly to the server it down our sever during build process, when build is success and complete then it move to server like digitalocean and netlify working. how can we do this in github action please help me?
Hi, Is it possible to create the pull request and make it merge automatically. If you push new changes to your repo and if all of the tests are passing the changes will merge otherwise the won't. So everything you need to do is just push new changes and that's it. I managed to create this ci cd pipeline on github actions but still I had to manually hit the "create pull request" button and then if the tests passed it automatically merged, but that's still not fully automated because of the create pull request step.
The merging of a PR that passes tests can be automated, but I'm not sure why you would want to automate the creating of a PR? Would this be on every commit to a branch?
@@tom.developer I’m working on a solo project so I thought of a way where I can push changes to a different branch than master and if the builds, tests and so on are passing it will automatically merge with the master branch. On a project where multiple people are working it is normal to create manually a PR because it still has to be reviewed by someone else, but in a solo project reviewing your own changes feels a bit unnecessary. I have managed to achieve that behavior so I don’t need any help, but I’m open for a discussion :)
Such a wonderful video Tom
This is amazing! Thanks for the tutorial. One of my main issues was I didn't want to test the cicd on production
You could set different environment variables for the test job. So the job for testing would use separate infrastructure that is designated for testing the code within a pull request. If the job is successful, you know that the code is working and it is ready to be merged :)
But you are using StrictHostKeyChecking=no which is not good (safe), right?
Very useful; i just checked if the video is playing on 1.5x😂. Just slow down a little bit and create more devops stuff man
Thanks for your feedback! I'm a fast talker but I'll do my best to slow it down next time :)
Hey Tom, amazing video. I'm curious though, what's the cool VS theme that you're using in this?
Thanks! I’m glad you enjoyed the video! My VS Code theme is Palenight :)
Great video Tom
Thanks Toby!
Many thanks Bro
You're welcome!
but how your code will deploy to a vps?
You can create a script that essentially performs the exact same commands that you would run in the command line to deploy your code. There are also packages that you can use in GitHub Actions which will allow you to do deployments, so check if there is one for your hosting provider as it could save you a lot of time! :)
Very useful! Thanks :)
You're welcome!
Which tools do you use for your videos? I like tge canera movement when you record your screen. How did you animate it like this?❤😂
I use Premiere Pro and After Effects for my editing. The camera movements are created by created a 3d scene and moving the camera around :)
@@tom.developer never saw so awesome edits from software engineer. Currently you are my favourite.😀
Nice video, but why they make build directly to the server it down our sever during build process, when build is success and complete then it move to server like digitalocean and netlify working. how can we do this in github action please help me?
Hey, I'm confused what you mean. Maybe I've misunderstood. Are you able to explain this one further :)
Hi, Is it possible to create the pull request and make it merge automatically. If you push new changes to your repo and if all of the tests are passing the changes will merge otherwise the won't. So everything you need to do is just push new changes and that's it. I managed to create this ci cd pipeline on github actions but still I had to manually hit the "create pull request" button and then if the tests passed it automatically merged, but that's still not fully automated because of the create pull request step.
The merging of a PR that passes tests can be automated, but I'm not sure why you would want to automate the creating of a PR? Would this be on every commit to a branch?
@@tom.developer I’m working on a solo project so I thought of a way where I can push changes to a different branch than master and if the builds, tests and so on are passing it will automatically merge with the master branch. On a project where multiple people are working it is normal to create manually a PR because it still has to be reviewed by someone else, but in a solo project reviewing your own changes feels a bit unnecessary. I have managed to achieve that behavior so I don’t need any help, but I’m open for a discussion :)
nice
Thanks!
Can you please blink
Nope 👀
Way too fast paced. Guess I'm just not the target audience for this
Sorry, you're the second person to give this feedback. I'll slow it down next time :)
Too fast, most useful for pro's and less for beginners.
Noted. Thank you for the feedback :)
Too fast, Not very beginner friendly. You were too fast as if you were going to paris the next minute
Sorry, I'll slow it down next time :)
It means that this video is not yet for you. It’s not the guy’s fault.