Merge pull request #22 from intersystems-community/stage

Stage

Author: nsolov

.github/workflows/trigger-deploy.yml

@@ -0,0 +1,26 @@
+# This workflow triggers deployment workflow in 'zpm-registry-deployment' repo
+# It was decided to separate them
+name: Trigger ZPM deployment
+
+on:
+  push:
+    branches:
+#      - master
+      - stage
+#  release:
+#    types:
+#      - created
+
+jobs:
+  trigger-zpm-deployment:
+    name: Trigger zpm-registry-deployment via REST API
+    runs-on: ubuntu-18.04
+
+    steps:
+    - name: REST POST call
+      run: |-
+        curl -X POST https://api.github.com/repos/intersystems-community/zpm-registry-deployment/dispatches \
+          -H 'Accept: application/vnd.github.everest-preview+json'                                          \
+          --user ${{ secrets.PAT_USERNAME }}:${{ secrets.PAT }}                                             \
+          --data "{\"event_type\": \"${{ github.event_name }}\", \"client_payload\": { \"zpm_ref_orig\": \"${GITHUB_REF##*/}\", \"zpm_commit_sha_orig\": \"$GITHUB_SHA\" }}"
+

README.md

@@ -17,8 +17,11 @@ Import classes from cls and run Installer from Root
 ## Docker Installation
 Build docker container
 
+## ZPM Installation
+`install zpm-registry`
+
 # Usage
-ZPM Registry exposes REST API, which perfoms listing, publising and deployment services. You can examine the REST in the source class [REgistry.cls](https://github.com/intersystems-community/zpm-registry/blob/master/src/cls/ZPM/Registry.cls) or via Swagger
+ZPM Registry exposes REST API, which perfoms listing, publising and deployment services. You can examine the REST in the source class [Registry.cls](https://github.com/intersystems-community/zpm-registry/blob/master/src/cls/ZPM/Registry.cls) or via Swagger
 
 Note, when you publish the repo via API you need to provide the GIthub URL of the repo, which will contain module.xml.
 And published package will remember the repository and will not allow to publish/update package with the same name but with another repository.