I am at the point in Chapter Five where I am ready to deploy. Do I need to do the git adds and git commit for the changes I have made before deploying? Below is what I get from git status:
On branch master
Changes not staged for commit:
(use “git add/rm …” to update what will be committed)
(use “git checkout – …” to discard changes in working directory)
Committing your changes to Git should have no bearing on the deployment of your project, regardless of whether it is iOS, .NET, Java, or otherwise. Git simply allows you to store your changes and allow other developers to use your code. When your launch your iOS project, you are launching from your machine, and not from your Git repository.
Having said that…
Yes, you should ensure that all of your changes, and updates are committed so that if anything should happen to your project, your changes are saved. It’s always good practice to commit changes regularly to ensure that individual commits are isolated from unrelated changes which allows you to track your changes better, and of course, ensure that your code repository is up to date.
@chriscrossen@syedfa actually for Vapor Cloud, you do need to commit your changes to Git before you can deploy to Vapor Cloud. Since Vapor Cloud clones your project from the remote repository (GitHub), your changes must be committed and pushed before you can deploy.
In Chapter 5 the vapor cloud deploy command should commit your changes for you, but you can do it manually with