'Suggestions please for working with Salesforce and Github on large orgs
I am trying to get my head round a feasible workflow when working on large Salesforce orgs (more than 100 apex classes).
At the moment we have a github repository with all the source code.
So I create a new branch for the work and clone the repository into a folder on my PC.
Then I use VS Code to add a feature / fix a bug.
The issue I have is that the folder hierarchy has over 6,000 files and feels unwieldy when working in VSCode.
Does anyone have a better workflow? One throught is to use the manifest to only pull the components I need from production, but that seems to bypass Git
thanks, Eamon
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|