Timeline for Working with GIT and org code in VS code for a single sandbox
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 24, 2019 at 13:20 | comment | added | David Reed | I'd respectfully suggest that this solution is a chimera. It is hobbled by a core architectural limitation - the single development org without deployment control - that prevents you from using source control or continuous integration in any best-practices sort of way. Instead of investing heavily in systems built around that limitation, I'd work to change it first. | |
| Sep 24, 2019 at 11:36 | history | edited | Sarang | CC BY-SA 4.0 |
added 305 characters in body
|
| Sep 23, 2019 at 19:22 | answer | added | Magnus Kreth | timeline score: 3 | |
| Sep 23, 2019 at 14:50 | comment | added | Sarang | @MagnusKreth : We want it because: 1. Backup, 2. We want devs to work in isolation but it won't be possible as we have single dev org for all, will it? 3. We want to maintain all code at one place. This means all code from various teams, modules that will finally go live in prod, but may not be related to each other. 4. We do not want to do deployments from repo. | |
| Sep 23, 2019 at 13:06 | comment | added | Magnus Kreth | And what goals are you trying to achieve with having a code repository? Should you're repository be a backup of your developments in the sandbox? Do you want to allow developers to work in isolation, e.g. seperate environments (Sandboxes/scratch orgs) and integrate in your repository? Do you want to create a deployment pipeline from your repo? Understanding your goals would make it much easier to recommend a possible solution. | |
| Sep 23, 2019 at 9:20 | history | edited | Sarang | CC BY-SA 4.0 |
added 47 characters in body
|
| Sep 23, 2019 at 9:14 | history | asked | Sarang | CC BY-SA 4.0 |