![deploying code from github to salesforce ant migration tool deploying code from github to salesforce ant migration tool](https://flosum.com/wp-content/uploads/2019/03/shutterstock_626630342-1-800x320.jpg)
Deploying code from github to salesforce ant migration tool how to#
But how to deploy pulled changes to a server? To start making any changes in a code you need to sync your local version with a sandbox. We can also pull changes from the remote and merge/rebase with yours. Ok, with separate sandboxes we can use Git and work in feature branches, push them to a remote repository and make pull requests. The following picture describes that model: I think it is applicable to any development process. Here you can find a successful branching model for Git.
![deploying code from github to salesforce ant migration tool deploying code from github to salesforce ant migration tool](https://cdn-images-1.medium.com/max/800/1*Y_sYLLlG9AMOjA4VIWC-4A.png)
There is a cool post about typical Salesforce + Git development process by Patrick Connelly and I will not repeat the things here. gitignore, here is my example for Sublime Mavens Mate. Anyway, Salesforce will convert your line endings to LF and you’ll receive the changes after updated your project from a server. There is a number of hints in Git configuration for Salesforce: It will allow every developer to make changes independently and create single task-related file versions. But how to use Git branches when you work in the same sandbox with other developers? What if 2 developers will make a change in the same class? The answer is pretty obvious: every developer should have own sandbox. If your code is not on Git – it is nowhere. Ok, let’s see how we can set up a good Salesforce development process with Git, Continuous Integration and comfortable deployment. 50 % of the Salesforce development companies I know even don’t use Git. It is so few open source libraries and frameworks. From my experience: it is so few really strong development teams in this area.Just imagine 2 Ruby developers making their changes at the same time on the same server! This makes standard development workflows with Git inappropriate for Salesforce. Developers make their changes directly in the cloud. Salesforce – is a cloud-based platform.I see 2 reasons of why it is so hard to find any useful posts about development processes with Salesforce: Does anybody like to waste time clicking and adding components to change sets? Set up salesforce development process I don’t even mention a standard process without a version control system usage and deployments via changesets. There is a bunch of posts about different techniques in development with Java, Ruby on Rails, and other popular languages & technologies, but not for Salesforce.