Going to give the video a watch now, as for the GIT issues we are experiencing it may just be user error and working with different team ownership over Healthshare pieces. The Management/Admin side of things is owned by another team than the developers and Admin is putting GIT into place. Currently they are implementing the Embedded git process and our developers have been hitting some snags with merging branches with main and then getting the code migrated to our next environment. The pipeline process is not there yet, just branching and source control over our lowest DEV environment. The push to use vscode over studio is there but the processes have not been migrated so we are still having to fall back to studio for deployments. The other side of things is the devlopers currently working on projects including myself are used to J2's Workbench Tools and GIT process which may have spoiled us.. haha
Thank you for the directional points on the embedded-git and git-source-control docs and strategies. Those will definitely help!
Since the approach sounds like to use Deployment Changes till the pipeline is in process for Git. If I am not caring about what is currently in a production in the target environment as its out of sync by a large degree. To bring it back into sync would I add the production class and ptd and all classes and ptd that I would like to be migrated or would adding the production class and ptd to the export cause any issues since there is already a production class present?
Thanks so much! I'll give that a watch!