Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • Thanks for your clear answer, I believe your solution is the best practice. However I think that on some cases more one developer need to work together in the same instance (for instance: one coding the VF page and the other coding the Apex Controller ). On small and middle size project that practice is faster than multiple instance. Are you agree? there is any alternative? Commented Oct 28, 2013 at 17:14
  • In real life, if you have two (trusted) devs working on the same feature, you are likely sharing a branch and an instance. You just need to be careful about editing the same file at the same time, clear communication is key here. I still think the best practice is to commit frequently and start with a pull. The only time to Refresh from Server is when creating new schema. In this world, if it's not committed, it does not exist. Commented Oct 28, 2013 at 17:26
  • @greenstork I think the concept of "it's not committed, it does not exist" is great, but what about those unsupported metadata types? They will refresh/pull from the Production Environment; is there any best practice for keeping that stored in GIT? salesforce.com/us/developer/docs/api_meta/Content/… Commented Sep 8, 2014 at 20:55