chore: expand prettier and ESLint globs

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -1,4 +1,4 @@
-name: "🐛 Bug report"
+name: '🐛 Bug report'
 description: Let us know about a bug!
 labels: ['bug']
 title: '[bug]'

.github/ISSUE_TEMPLATE/documentation-issues.yml

@@ -1,4 +1,4 @@
-name: "📚 Documentation issues"
+name: '📚 Documentation issues'
 description: Make a suggestion to improve the documentation!
 labels: ['documentation']
 title: '[docs]'

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -1,4 +1,4 @@
-name: "🎁 Feature request"
+name: '🎁 Feature request'
 description: Suggest a new feature/enhancement!
 labels: ['enhancement']
 title: '[feat req]'

.github/workflows/codeql-analysis.yml

@@ -1,8 +1,9 @@
-name: "Code scanning - action"
+name: 'Code scanning - action'
 
 on:
   push:
-    branches-ignore: "dependabot/**"
+    branches-ignore:
+      - 'dependabot/**'
   pull_request:
     paths-ignore:
       - '**.md'
@@ -11,7 +12,6 @@ on:
 
 jobs:
   CodeQL-Build:
-
     # CodeQL runs on ubuntu-latest and windows-latest
     runs-on: ubuntu-latest
 
@@ -22,10 +22,10 @@ jobs:
       # Initializes the CodeQL tools for scanning.
       - name: Initialize CodeQL
         uses: github/codeql-action/init@v1
+
         # Override language selection by uncommenting this and choosing your languages
         # with:
         #   languages: go, javascript, csharp, python, cpp, java
-
       # Autobuild attempts to build any compiled languages  (C/C++, C#, or Java).
       # If this step fails, then you should remove it and run the build manually (see below)
       - name: Autobuild

.github/workflows/test.yml

@@ -10,7 +10,6 @@ on:
       - '**.md'
 
 jobs:
-
   build:
     name: Build
 

.prettierignore

@@ -1,3 +1,4 @@
 dist/
 lib/
 node_modules/
+.licenses/

.prettierrc.json

@@ -6,6 +6,5 @@
   "singleQuote": true,
   "trailingComma": "none",
   "bracketSpacing": false,
-    "arrowParens": "avoid",
+  "arrowParens": "avoid"
-    "parser": "typescript"
 }

CODE_OF_CONDUCT.md

@@ -14,21 +14,21 @@ appearance, race, religion, or sexual identity and orientation.
 Examples of behavior that contributes to creating a positive environment
 include:
 
-* Using welcoming and inclusive language
+- Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
+- Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
+- Gracefully accepting constructive criticism
-* Focusing on what is best for the community
+- Focusing on what is best for the community
-* Showing empathy towards other community members
+- Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or
+- The use of sexualized language or imagery and unwelcome sexual attention or
   advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
+- Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
+- Public or private harassment
-* Publishing others' private information, such as a physical or electronic
+- Publishing others' private information, such as a physical or electronic
   address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
+- Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
 ## Our Responsibilities

CONTRIBUTING.md

@@ -32,8 +32,8 @@ Artifact related issues will be tracked in this repository so please do not open
 6. Make sure your code is correctly formatted: `npm run format`
 7. Make sure your code passes linting: `npm run lint`
 8. Update `dist/index.js` using `npm run release`. This creates a single javascript file that is used as an entry-point for the action
-7. Push to your fork and [submit a pull request][pr]
+9. Push to your fork and [submit a pull request][pr]
-8. Pat your self on the back and wait for your pull request to be reviewed and merged.
+10. Pat your self on the back and wait for your pull request to be reviewed and merged.
 
 Here are a few things you can do that will increase the likelihood of your pull request being accepted:
 

package.json

@@ -7,9 +7,9 @@
     "build": "tsc",
     "release": "ncc build src/upload-artifact.ts && git add -f dist/",
     "check-all": "concurrently \"npm:format-check\" \"npm:lint\" \"npm:test\" \"npm:build\"",
-    "format": "prettier --write **/*.ts",
+    "format": "prettier --write .",
-    "format-check": "prettier --check **/*.ts",
+    "format-check": "prettier --check .",
-    "lint": "eslint **/*.ts",
+    "lint": "eslint .",
     "test": "jest --testTimeout 10000"
   },
   "repository": {