Merge pull request #816 from cambot/feature/add-xslts-to-baseline

Enhance baseline to include XSL transforms.

Author: isc-pbarton

CHANGELOG.md

@@ -7,6 +7,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [2.13.0] - Unreleased
 
+### Added
+- Expanded Baseline Export to include XSL Transforms (#815)
+
 ### Fixed
 - Fix Import All not importing items that do not already exist when compileOnImport is not set (#798)
 - Fix baselining output more consistent, human readable (#814)

README.md

@@ -10,7 +10,7 @@ Embedded Git support for InterSystems platforms, supporting unified source contr
 
 ## Installation and Setup
 
-1. Load this repository into IRIS from the community package registry. 
+1. Load this repository into IRIS from the community package registry.
     ```
     zpm "install git-source-control"
     ```
@@ -24,7 +24,7 @@ Embedded Git support for InterSystems platforms, supporting unified source contr
    d ##class(SourceControl.Git.API).Configure()
    ```
    This will also allow you to generate an SSH key for use as (e.g.) a deploy key and to initialize or clone a git repo.
-3. If using VSCode: Set up `isfs` server-side editing. First, save your current workspace in which you have the code open. Then, open the `.code-workspace` file generated by VS Code and add the following to the list of folders: 
+3. If using VSCode: Set up `isfs` server-side editing. First, save your current workspace in which you have the code open. Then, open the `.code-workspace` file generated by VS Code and add the following to the list of folders:
     ```
     {
         "name": "<whatever you want the folder to show up as in the project explorer view>",
@@ -87,6 +87,8 @@ This might look like:
 
 ![Example of mapping configuration](docs/images/settings.PNG "Example of mapping configuration")
 
+Additional documentation on file types [can be found here](https://docs.intersystems.com/services/csp/docbook/DocBook.UI.Page.cls?KEY=AGITLAB#AGITLAB_settings_mappings).
+
 ### Baselining Source Code
 If enabling source control on an existing system, you will need to create a baseline by exporting all existing items to the Git repository. See [our documentation on baselining](/docs/baselining.md).
 

cls/SourceControl/Git/Utils.cls

@@ -1571,19 +1571,19 @@ ClassMethod ImportRoutines(force As %Boolean = 0, pullEventClass As %String) As
     // If there is a config file it must be imported before everything else.
     if $Data(itemList(##class(SourceControl.Git.Settings.Document).#INTERNALNAME)) {
         set sc = ##class(SourceControl.Git.Utils).ImportItem(##class(SourceControl.Git.Settings.Document).#INTERNALNAME, force)
-        
+
         if $$$ISERR(sc) {
             set ec = $$$ADDSC(ec, sc)
         } else {
             kill err, itemList
             set err = 0
-            
+
             // Get the item list again as it may be different after just importing the config file
             set ec = $$$ADDSC(ec, ..ListItemsInFiles(.itemList, .err))
         }
         quit:'ec ec
     }
-    
+
     kill files
 
     set settings = ##class(SourceControl.Git.Settings).%New()
@@ -3047,7 +3047,7 @@ ClassMethod BaselineExport(pCommitMessage = "", pPushToRemote = "") As %Status
     try {
         write !, "Exporting items..."
         set rs = ##class(%Library.RoutineMgr).StudioOpenDialogFunc(
-            "*.mac,*.int,*.inc,*.cls,*.csp,*.HL7,*.LUT,*.AST,*.X12"
+            "*.mac,*.int,*.inc,*.cls,*.csp,*.xsl,*.HL7,*.LUT,*.AST,*.X12"
             , , ,0  // SystemFiles
             ,1      // Flat
             ,0      // NotStudio