Checkout branch deploys changes
I'm not sure if this is a feature or a bug. Regardless it poses an issue with us since we work in shared dev orgs at the moment.
If I'm working on FEAT-1 and make changes to MyClass1.cls, then checkout a new branch (FEAT-2), MyClass1.cls will be deployed automatically and my changes will be overwritten. This seems to be triggered immediately after switching branches.
I've unchecked what I thought would prevent this in the Synchronization settings in the IDE (see attachment).
The current workaround is to completely exit the IDE before switching branches, then re-open the IDE afterwards. Of course this is not ideal and renders the integrated VCS feature of the IDE useless.
What are your thoughts?
Comments (6)
-
repo owner -
repo owner - changed component to Deployment and Retrieval
-
assigned issue to
-
Account Deactivated reporter Thanks Scott! I didn't mean to use such strong language when I said it renders it useless, so please forgive me.
-
repo owner - changed version to 1.7.1.7
-
repo owner - changed status to resolved
Should be resolved with changes in 1.7.1.7.
-
repo owner - changed component to Metadata Deployment/Retrieval/Removal
- Log in to comment
It's definitely an issue that needs to be addressed. I'm not sure I'd say that it renders the integrated VCS features useless, but it certainly presents a problem around a key one. Let me take a look and see what I can do to avoid auto-deployment on those types of events. Hopefully this is something I can resolve in short cycle. I'll keep you posted here.