Skip to content

Update hcc.md #708

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 18, 2025
Merged

Update hcc.md #708

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions docs/hcc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.

Expand All @@ -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
<!-- - [Official Change Control Documentation](https://docs.intersystems.com) -->
- [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

Expand Down Expand Up @@ -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.
* live branch: the protected branch associated with a Protected Namespace in the Prod Deployment. This branch is automatically present in the GitLab repository.
Loading