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.
- 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?Martin Borthiry– Martin Borthiry2013-10-28 17:14:05 +00:00Commented 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.greenstork– greenstork2013-10-28 17:26:01 +00:00Commented 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/…zainogj– zainogj2014-09-08 20:55:44 +00:00Commented Sep 8, 2014 at 20:55
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. marketing-cloud), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
default