Merge pull request #3 from AgencyPMG/ALLI-10561-alli-data-backend-update-pmg-bull-arena-to-be-compatible-with-bull-mq

Alli 10561 alli data backend update pmg bull arena to be compatible with bull mq

Author: JZhang502

.dockerignore

@@ -0,0 +1,46 @@
+module.exports = {
+  env: {
+    node: true,
+    es6: true,
+    browser: true,
+    commonjs: true,
+    jquery: true,
+  },
+  parserOptions: {
+    ecmaVersion: 2018,
+  },
+  plugins: ['prettier'],
+  extends: ['prettier'],
+  overrides: [
+    {
+      files: ['lib/**'],
+      rules: {
+        'max-len': 'error',
+      },
+    },
+    {
+      files: ['benchmark/**', 'examples/**'],
+      parserOptions: {
+        ecmaVersion: 8,
+      },
+      rules: {
+        'no-console': 'off',
+      },
+    },
+    {
+      files: ['test/**'],
+      parserOptions: {
+        ecmaVersion: 2017,
+        sourceType: 'module',
+      },
+      rules: {
+        'handle-callback-err': 'warn',
+        'no-shadow': 'off',
+        'no-warning-comments': 'off',
+      },
+    },
+  ],
+  rules: {
+    strict: 'off',
+  },
+};

.eslintrc.js

@@ -0,0 +1,11 @@
+version: 2
+updates:
+  - package-ecosystem: npm
+    directory: '/'
+    schedule:
+      interval: daily
+    open-pull-requests-limit: 10
+    versioning-strategy: widen
+    commit-message:
+      prefix: chore
+      include: scope

.github/dependabot.yml

@@ -0,0 +1,12 @@
+#### Changes Made
+
+#### Potential Risks
+<!--- What can go wrong with this change? How will these changes affect adjacent code/features? How will we handle any adverse issues? --->
+
+#### Test Plan
+<!--- How do we know this PR does what it's supposed to do? How do we ensure that adjacent code/features are still working? How do we evaluate the performance implications of this PR?--->
+
+#### Checklist
+
+- [ ] I've increased test coverage
+- [ ] Since this is a public repository, I've checked I'm not publishing private data in the code, commit comments, or this PR.

.github/pull_request_template.md

@@ -0,0 +1,74 @@
+# This workflow will do a clean install of node dependencies, and run the linter
+# For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions
+
+name: Node.js CI
+
+on:
+  # Any additional branches here will currently be treated as release (or maintenance) branches.
+  # if the need to run jobs on other branches emerges, then the release job will need a better
+  # condition expression.
+  push:
+    branches: [master, 2.x]
+  pull_request:
+    branches: [master, 2.x]
+
+jobs:
+  lint:
+    # https://github.community/t/github-actions-does-not-respect-skip-ci/17325/9
+    if: "!contains(github.event.head_commit.message, '[skip ci]')"
+    runs-on: ubuntu-latest
+
+    env:
+      NPM_AUTH_TOKEN: '${{ secrets.NPM_AUTH_TOKEN }}'
+
+    strategy:
+      matrix:
+        node-version: [10.x, 12.x, 14.x]
+
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          # For commitlint; ideally this would only check out the feature branch's history, but
+          # that's not currently an option.
+          fetch-depth: ${{ github.event_name == 'push' }}
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v3
+        with:
+          node-version: ${{ matrix.node-version }}
+      - name: set up npmrc
+        run: echo "//registry.npmjs.org/:_authToken=${{secrets.NPM_AUTH_TOKEN}}" > .npmrc
+      - run: npm ci
+      - run: npm run ci --if-present
+      - run: npm run ci:commitlint
+        if: "github.event_name != 'push' && github.actor != 'dependabot[bot]'"
+        env:
+          GITHUB_BASE_REF: ${{ github.event.pull_request.base.ref }}
+
+  release:
+    # https://github.community/t/github-actions-does-not-respect-skip-ci/17325/9
+    if: "github.event_name == 'push' && !contains(github.event.head_commit.message, '[skip ci]')"
+    runs-on: ubuntu-latest
+
+    needs: [lint]
+
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          # Necessary to prevent the checkout action from writing credentials to .git/config, which
+          # semantic-release attempts to use to push despite those credentials being denied the
+          # push.
+          # See https://github.com/semantic-release/git/issues/196#issuecomment-601310576.
+          persist-credentials: false
+      - name: Use Node.js 14.x
+        uses: actions/setup-node@v3
+        with:
+          node-version: 14.x
+      - name: set up npmrc
+        run: echo "//registry.npmjs.org/:_authToken=${{secrets.NPM_AUTH_TOKEN}}" > .npmrc
+      - run: npm ci
+      - name: Release
+        run: npx semantic-release -b master,2.x
+        env:
+          # Need to use a separate token so we can push to the protected default branch.
+          GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
+          NPM_AUTH_TOKEN: '${{ secrets.NPM_AUTH_TOKEN }}'

.github/workflows/node.js.yml

@@ -1,2 +1,8 @@
 node_modules
+package-lock.json
 *.DS_Store
+.vscode
+.idea
+*.tern-port
+*.sublime-workspace
+dump.rdb

.gitignore

@@ -0,0 +1 @@
+_

.husky/.gitignore

@@ -0,0 +1,5 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+npm run pretty:quick
+npm run lint:staged

.husky/pre-commit

@@ -0,0 +1,3 @@
+{
+  "*.{js}": "node_modules/.bin/eslint . --ignore-path ./.prettierignore --fix"
+}

.lintstagedrc

@@ -0,0 +1,4 @@
+*.hbs
+*.min.js
+*.min.css
+pull_request_template.md