Skip to main content

We’re currently working on a MuleSoft + Salesforce integration project where multiple developers collaborate using Bitbucket and SharePoint. A recurring issue we've encountered is code being overwritten when developers work in isolation for several days without pulling the latest changes from the remote repository. For example, one developer might push updates today, and another—who has been working on the same files offline for a week—later pushes their changes without pulling, unintentionally overwriting previous updates. This lack of synchronization and alerting has led to deployment issues and lost work. We're now exploring solutions to enforce Git best practices such as using feature branches, requiring pull requests with merge checks, protecting the main branch from direct commits, and setting up alerts or webhooks to notify teams of remote updates. We’re also interested in any tools or strategies the community recommends for avoiding these types of conflicts, especially when using Bitbucket and SharePoint together in a multi-developer setup

@* Salesforce Developers * 

1 Antwort
0/9000