Fix merge conflicts

Author: tannerdolby

.github/ISSUE_TEMPLATE/a11y-feature-request.md

@@ -2,7 +2,7 @@
 name: ♿ A11y feature request
 about: Suggest an idea for a new a11y feature
 title: '[A11Y FEATURE]: <title>'
-labels: a11y-feature
+labels: 'a11y feature'
 
 ---
 
@@ -25,8 +25,8 @@ labels: a11y-feature
 <!--
   Provide a bullet-pointed list of acceptance criteria.
 -->
-- 
-- 
+- [ ] 
+- [ ] 
 
 
 ## Why is this a11y feature important?

.github/ISSUE_TEMPLATE/bug-report.md

@@ -35,8 +35,8 @@ Checka11y.css version:
 <!--
   Provide a bullet-pointed list of acceptance criteria.
 -->
-- 
-- 
+- [ ] 
+- [ ] 
 
 ## Why is fixing this bug important?
 <!--

.github/ISSUE_TEMPLATE/documentation.md

@@ -22,8 +22,8 @@ labels: documentation
 <!--
   Provide a bullet-pointed list of acceptance criteria.
 -->
-- 
-- 
+- [ ] 
+- [ ] 
 
 
 ## Why is this important?

.github/ISSUE_TEMPLATE/project-enhancement-idea.md

@@ -2,7 +2,7 @@
 name: 💻 Project enhancement/maintenance idea
 about: Suggest an idea for a project enhancement or maintenance
 title: '[ENHANCEMENT]: <title>'
-labels: project-enhancement
+labels: 'project enhancement'
 
 ---
 
@@ -23,8 +23,8 @@ labels: project-enhancement
 <!--
   Provide a bullet-pointed list of acceptance criteria.
 -->
-- 
-- 
+- [ ] 
+- [ ] 
 
 
 ## Why is this enhancement or maintenance important?

.github/PULL_REQUEST_TEMPLATE/a11y-feature.md

@@ -1,7 +1,7 @@
 ---
 name: ♿ A11y feature
 about: Submit a new a11y feature
-labels: a11y-feature
+labels: 'a11y feature'
 title: '[A11Y FEATURE]: <title>'
 ---
 
@@ -16,7 +16,7 @@ title: '[A11Y FEATURE]: <title>'
 <!--
   Explain why this feature is important to have in Checka11y.css.
   Provide any relevant links to back up your reasoning.
-  If this pull request resolves an `a11y-feature` issue, you can leave this section out and just put "This is described in the linked issue."
+  If this pull request resolves an `a11y feature` issue, you can leave this section out and just put "This is described in the linked issue."
 -->
 
 ## Covered test cases
@@ -27,7 +27,7 @@ title: '[A11Y FEATURE]: <title>'
 ### Did you test on all major browsers?
 <!--
   Put an `x` in all the boxes that apply.
-  If not, please add a brief explanation as to why you couldn't (e.g. "I couldn't test Safari because I don't have access to an Apple device).
+  If not, please add a brief explanation as to why you couldn't (e.g. "I couldn't test Safari because I don't have access to an Apple device").
 -->
 - [ ] Chrome
 - [ ] Firefox

.github/PULL_REQUEST_TEMPLATE/bug-fix.md

@@ -33,7 +33,7 @@ title: '[BUG FIX]: <title>'
 ### Did you test on all major browsers?
 <!--
   Put an `x` in all the boxes that apply.
-  If not, please add a brief explanation as to why you couldn't (e.g. "I couldn't test Safari because I don't have access to an Apple device).
+  If not, please add a brief explanation as to why you couldn't (e.g. "I couldn't test Safari because I don't have access to an Apple device").
 -->
 - [ ] Chrome
 - [ ] Firefox

.github/PULL_REQUEST_TEMPLATE/project-enhancement.md

@@ -1,7 +1,7 @@
 ---
 name: 🚀 Project enhancement
 about: Submit an enhancement or maintenance
-labels: project-enhancement
+labels: 'project enhancement'
 title: '[ENHANCEMENT]: <title>'
 ---
 
@@ -16,7 +16,7 @@ title: '[ENHANCEMENT]: <title>'
 <!--
   Explain why this enhancement or maintenance is important to have in Checka11y.css.
   Provide any relevant links to back up your changes.
-  If this pull request resolves a `project-enhancement` issue, you can leave this section out and just put "This is described in the linked issue."
+  If this pull request resolves a `project enhancement` issue, you can leave this section out and just put "This is described in the linked issue."
 -->
 
 ## Covered test cases
@@ -27,7 +27,7 @@ title: '[ENHANCEMENT]: <title>'
 ### Did you test on all major browsers?
 <!--
   Put an `x` in all the boxes that apply.
-  If not, please add a brief explanation as to why you couldn't (e.g. "I couldn't test Safari because I don't have access to an Apple device).
+  If not, please add a brief explanation as to why you couldn't (e.g. "I couldn't test Safari because I don't have access to an Apple device").
 -->
 - [ ] Chrome
 - [ ] Firefox

.github/workflows/Build.yml

@@ -0,0 +1,53 @@
+name: Pipeline
+
+on:
+  push:
+    branches:
+    - master
+  pull_request:
+    branches:
+    - master
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: Install Node
+        uses: actions/setup-node@v2
+        with:
+          node-version: '14.x'
+      - name: Clean install npm dependencies
+        run: npm ci
+      - name: Check project can build successfully
+        run: npm run build
+      - name: Check git is still clean after building
+        run: npm run has-no-changes
+      - name: Check project linting
+        run: npm run lint:check
+  tests:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: cypress-io/github-action@v2
+        with:
+          browser: chrome
+          headless: true
+          spec: "cypress/integration/*"
+  publish:
+    needs: [build, tests]
+    if: github.ref == 'refs/heads/master'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: Install Node
+        uses: actions/setup-node@v2
+        with:
+          node-version: '14.x'
+      - name: Clean install npm dependencies
+        run: npm ci
+      - name: Publish to npm
+        uses: JS-DevTools/npm-publish@v1
+        with:
+          token: ${{ secrets.NPM_TOKEN }}
+          check-version: true