You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+16-7Lines changed: 16 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,24 +42,33 @@ This will create the appropriate mappings to have all namespaces on the system u
42
42
43
43
## Basic Use
44
44
45
+
The point of Embedded Git is to intercept events made through all editors - both IDEs and the management portal - so that changes are reflected in the filesystem, in a git repo, and able to be shared with others. There are also source-control specific menus to help you do key tasks.
46
+
45
47
### Source Control
46
48
47
49
For those with less experience using source control, we recommend this [page](/docs/scintro.md) for a quick introduction to source control / change control basics.
48
50
49
51
### Health Connect Cloud
50
-
git-source control is the recommended source control for Health Connect Cloud. [This page](/docs/hcc.md) covers HCC specific usage of git-source-control, including the recommended development workflow, initial setup, and CICD pipelining.
52
+
53
+
git-source control is the recommended source control for Health Connect Cloud. [This page](/docs/hcc.md) covers HCC specific usage of git-source-control, including the recommended development workflow, initial setup, and CI/CD pipelining.
51
54
52
55
### VSCode
53
-
The same right click menus as in Studio live under "Server Source Control..." when right-clicking in a file (in the editor) or on a file when exploring an isfs folder. The top level "source control" menu is accessible through the command palette or the source control icon in the top right of the editor.
54
56
55
-
### Studio
57
+
Source control menus will appear under "Server Source Control..." when right-clicking in a file (in the editor) or on a file when exploring an isfs folder. The top level "source control" menu is accessible through the command palette or the source control icon in the top right of the editor.
56
58
57
-
Note: Studio has been deprecated. VSCode is the IDE recommended by InterSystems.
59
+
For full details on all of the menu items, see [this reference page](/docs/menu-items.md).
60
+
61
+
### Management Portal Editors
58
62
59
-
Add an existing file for tracking by right-clicking on it in the workspace/project view and choosing Git > Add.
60
-
This same menu also has options to remove (stop tracking the file), discard changes (revert to the index), or commit changes.
63
+
In relevant editors in the management portal, there are two icons that allow access to the same source control functionality as in IDEs. Click the source control icon to see the menu, and the clipboard to see output from previously run commands in your browser session.
64
+
65
+
*Important*: if using source control for interoperability, check the "Permit Enabling Automatic Refresh of Management Portal Pages" box in the management portal, at the page: Interoperability > Manage > Configuration > Interoperability Settings. This mitigates a potential for lost work.
66
+
67
+
### Studio
68
+
69
+
Note: Studio has been deprecated. VSCode is the IDE recommended by InterSystems.
61
70
62
-
You can browse file history and commit changes through a user interface launched from the top level Git > "Launch Git UI" menu item. There is also a page for configuring settings.
71
+
That said, the same menu items and editor behavior will also work in Studio. There is a top-level "Git" menu with access to various operations and pages dependent on the current editor context.
0 commit comments