I wouldn’t suggest doing automatic deployment to the live site.
The trepidation might be because you haven’t mentioned automated testing even once in this article? I know this is a very basic introduction but testing is such a fundamental part of development that it really should be taught right at the start.
There are even tools now to make automated testing much easier (such as travis-ci) which could be integrated into the workflow you describe.
* Edit your files locally as before, testing them through a web server on your own computer and running your automated test suite.
* Commit your changes to your local Git repository on your feature branch
* Push changes to the remote repository.
* Create a pull request to your master branch
* Wait for Travis to run your test suit
* Once all tests pass merge into your master branch
* Log into the deployment service.
* Hit the Deploy now button.
* Preview the changes.
* Run the deployment and then check your live site.
Aaron Bassett
The trepidation might be because you haven’t mentioned automated testing even once in this article? I know this is a very basic introduction but testing is such a fundamental part of development that it really should be taught right at the start.
There are even tools now to make automated testing much easier (such as travis-ci) which could be integrated into the workflow you describe.
* Edit your files locally as before, testing them through a web server on your own computer and running your automated test suite.
* Commit your changes to your local Git repository on your feature branch
* Push changes to the remote repository.
* Create a pull request to your master branch
* Wait for Travis to run your test suit
* Once all tests pass merge into your master branch
* Log into the deployment service.
* Hit the Deploy now button.
* Preview the changes.
* Run the deployment and then check your live site.