You're correct. But you should be able to test the code on your machine and make sure it's correct before committing it.
Your development machine should be able to run the same code as your server.
Making changes to the public site is a very bad practice. What if your code has errors in it?
Version control also keeps everyone up to date. Before making a change to the site you'll download the most up to date version from the repository, that way your local copy has everyones changes, with comments about what they've done.
Of course I'm not thinking about making changes to the public site. At the moment there is no public site, so I'm just thinking about a good development practice. I think that when the site will be public we may have a development copy of it on the server itself. I think we need to try it in practice, because we also have many doubts about resolving conflicts and merging.
Comments
You're correct. But you should be able to test the code on your machine and make sure it's correct before committing it.
Your development machine should be able to run the same code as your server.
Making changes to the public site is a very bad practice. What if your code has errors in it?
Version control also keeps everyone up to date. Before making a change to the site you'll download the most up to date version from the repository, that way your local copy has everyones changes, with comments about what they've done.
Of course I'm not thinking about making changes to the public site. At the moment there is no public site, so I'm just thinking about a good development practice. I think that when the site will be public we may have a development copy of it on the server itself. I think we need to try it in practice, because we also have many doubts about resolving conflicts and merging.