Harness CI pipeline

.harness/orgs/PROD/projects/Harness_Split/pipelines/javascript-sync-tools.yaml

@@ -0,0 +1,80 @@
+pipeline:
+  name: javascript-sync-tools
+  identifier: javascriptsynctools
+  projectIdentifier: Harness_Split
+  orgIdentifier: PROD
+  tags: {}
+  properties:
+    ci:
+      codebase:
+        connectorRef: fmegithubharnessgitops
+        repoName: javascript-sync-tools
+        build: <+input>
+  stages:
+    - stage:
+        name: Check-Test-Build
+        identifier: Checkout_code
+        description: ""
+        type: CI
+        spec:
+          cloneCodebase: true
+          caching:
+            enabled: true
+            override: true
+            paths: []
+          platform:
+            os: Linux
+            arch: Amd64
+          runtime:
+            type: Cloud
+            spec:
+              size: small
+              imageSpec:
+                imageName: ubuntu-latest
+          execution:
+            steps:
+              - step:
+                  type: Run
+                  name: Install and run redis-server
+                  identifier: redis_server
+                  spec:
+                    shell: Sh
+                    command: |-
+                      apt-get update && apt-get install -y redis-server
+                      redis-server --daemonize yes
+              - step:
+                  type: Action
+                  name: Set up Node.js
+                  identifier: Set_up_Nodejs
+                  spec:
+                    uses: dcodeIO/setup-node-nvm@master
+                    with:
+                      node-version: lts/*
+              - step:
+                  type: Run
+                  name: npm ci
+                  identifier: npm_ci
+                  spec:
+                    shell: Sh
+                    command: npm ci
+              - step:
+                  type: Run
+                  name: npm run check
+                  identifier: npm_run_check
+                  spec:
+                    shell: Sh
+                    command: npm run check
+              - step:
+                  type: Run
+                  name: npm run test
+                  identifier: npm_run_test
+                  spec:
+                    shell: Sh
+                    command: npm run test
+              - step:
+                  type: Run
+                  name: npm run build
+                  identifier: npm_run_build
+                  spec:
+                    shell: Sh
+                    command: npm run build

.harness/orgs/PROD/projects/Harness_Split/pipelines/javascriptsynctools/input_sets/javascript-sync-tools.yaml

@@ -0,0 +1,15 @@
+inputSet:
+  name: javascript-sync-tools
+  tags: {}
+  identifier: javascriptsynctools
+  orgIdentifier: PROD
+  projectIdentifier: Harness_Split
+  pipeline:
+    identifier: javascriptsynctools
+    properties:
+      ci:
+        codebase:
+          build:
+            type: branch
+            spec:
+              branch: <+trigger.branch>

CONTRIBUTORS-GUIDE.md

@@ -8,7 +8,7 @@ Split JavaScript Sync Tools is an open source project and we welcome feedback an
 
 1. Fork the repository and create a topic branch from `development` branch. Please use a descriptive name for your branch.
 2. Run `nvm use` to ensure that you are using the right npm and Node.js version, and `npm install` to have the dependencies up to date.
-3. While developing, use descriptive messages in your commits. Avoid short or meaningless sentences like: "fix bug".
+3. While developing, use descriptive messages in your commits. Avoid short or meaningless sentences like "fix bug".
 4. Make sure to add tests for both positive and negative cases.
 5. Run the linter script of the project and fix any issues you find.
 6. Run the build script and make sure it runs with no errors.