diff --git a/docs/hcc.md b/docs/hcc.md index fe254eb6..3c26f588 100644 --- a/docs/hcc.md +++ b/docs/hcc.md @@ -1,5 +1,8 @@ # Change Control with Embedded Git for Health Connect Cloud +## Start Here +It is highly recommended to start with the following online course: [Building Health Connect Cloud Interfaces with Source Control](https://learning.intersystems.com/course/view.php?id=2641). + ## General The recommended workflow for Health Connect Cloud is to: create an interface branch, make changes, sync them to GitLab, create a merge request, review and approve the merge request, and then test the changes after they are automatically deployed into a protected namespace. @@ -22,7 +25,7 @@ A Health Connect Cloud Dev deployment will have at least one Protected Namespace - Onboard customers on source control tools for Health Connect Cloud - Maintain change control documentation and videos - - [Learning Videos](https://learning.intersystems.com/course/view.php?name=HCCSourceControlUI) + - [Learning Videos](https://learning.intersystems.com/course/view.php?id=2641) # InterSystems-Recommended Workflow - Embedded Git and GitLab @@ -177,4 +180,4 @@ Some users may prefer a client-side source control approach instead of Embedded * protected branch: a branch in Git to which all commits must originate from a merge request * development branch: the protected branch associated with a Protected Namespace in the Dev Deployment. This branch is automatically present in the GitLab repository. * test branch: the protected branch associated with a Protected Namespace in the Test Deployment. This branch is automatically present in the GitLab repository. -* live branch: the protected branch associated with a Protected Namespace in the Prod Deployment. This branch is automatically present in the GitLab repository. \ No newline at end of file +* live branch: the protected branch associated with a Protected Namespace in the Prod Deployment. This branch is automatically present in the GitLab repository.