adding stuff for PT and TM

.github/workflows/compliance-workflow.yml

@@ -3,9 +3,9 @@ name: CyDig Compliance Workflow
 on:
   workflow_dispatch:
   schedule:
-    - cron: "0 1 * * 1-5"
+    - cron: '0 1 * * 1-5'
 
 jobs:
-    CyDig-Compliance-Workflow:
-      uses: Omegapoint/cydig-reusable-workflows/.github/workflows/compliance-template.yml@main
-      secrets: inherit
+  CyDig-Compliance-Workflow:
+    uses: Omegapoint/cydig-reusable-workflows/.github/workflows/compliance-template.yml@main
+    secrets: inherit

.github/workflows/test.yml

@@ -1,4 +1,4 @@
-name: test action 
+name: test action
 run-name: ${{ github.actor }} is running tests
 permissions:
   contents: read
@@ -23,4 +23,5 @@ jobs:
         uses: ./
         with:
           cydigConfigPath: ${{ github.workspace }}/src/cydigConfig.json
-          PAT-token: ${{ secrets.MY_GITHUB_PAT}}
+          PAT-token: ${{ secrets.MY_GITHUB_PAT}}
+          accessTokenAzureDevOps: ${{ DEVOPS_TOKEN_WORK_ITEMS }}

README.md

@@ -39,22 +39,22 @@ npm run format:write
 ```
 
 3. If you are developing a new control, create a new folder for your control in the ```src``` folder.
-4. Start developing. To compile your code, run the following command:


+4. Start developing. To compile your code, run the following command:
 
 ```bash
 npm run build
 ```
 
-5. To run the tests, run the following command:



+5. To run the tests, run the following command:
 
-```bash

+```bash
 npm run test
 ```
 
-To generated test results in a XML-file, run the following command:


+To generated test results in a XML-file, run the following command:
 
-```bash

-npm run testScript

+```bash
+npm run testScript
 ```
 
 6. If necessary, add input parameter in ```action.yml```, if it is needed for the control.
@@ -66,4 +66,4 @@ npm run testScript

 ## Creating a release for the action
 At cydig, we follow [Semantic Versioning](https://semver.org/) for our action releases. Practically, this means that when you're developing and creating a pull request (PR), you can assign one of three labels to the PR: Major, Minor, or Patch. These labels correspond to version numbers in the format vX.Y.Z, where X is the major version, Y is the minor version, and Z is the patch version.For example, if you add the "Patch" label to your PR, and it's approved and merged, a workflow will automatically run to create a release for the action. Here's an illustration of how the version number would change before and after the PR:
 * Version before PR: v1.0.1
-* Version after PR: v1.0.2
+* Version after PR: v1.0.2

action.yml

@@ -11,6 +11,10 @@ inputs:
     description: 'Automatic token from Github workflow'
     required: true
     default: 'Not working'
+  accessTokenAzureDevOps:
+    description: 'Personal access token for Azure DevOps with scope Work Items:read'
+    required: false
+    default: 'Not working'
 runs:
   using: node16
   main: dist/index.js

package.json

@@ -26,6 +26,7 @@
     "@actions/core": "^1.10.0",
     "@actions/github": "^5.1.1",
     "@vercel/ncc": "^0.36.1",
+    "azure-devops-node-api": "^12.4.0",
     "joi": "^17.10.1"
   },
   "devDependencies": {