Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. It only takes a minute to sign up.
Sign up to join this community
Every time I switch the source for my project (between sandboxes or between production and a sandbox) it defaults to "Work Online", and I need to remember to switch that or else it starts deploying things willy nilly.
I'm using version control, so I want to be in control of what's on the server and what's not. I think I may have accidentally saved something to my production org because I didn't remember to uncheck that (there's a deployment with a random hash name that says I deployed it).
The way we typically manage this flow as consultants (at least in my experience) is to have one repository/project per org. You should never change the source org for any of your projects locally.
When using the Force.com IDE to manage multiple instances, I use a naming convention that indicates production/sandbox, client, and sandbox name. What that looks like for me is something like:
Your version control will then have a detailed view of your development flow. You will see very granular changes in dev, then hopefully some bigger chunks and some reactive in staging, and ideally only complete feature deployments in each commit to your production repository.
dev to staging, you merge from the one repo into the other?
– Nathan Hinchey
Mar 12 '18 at 16:46
