chore: use pnpm and github actions

Author: jaredLunde

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,17 +1,17 @@
 ---
 name: Bug report
 about: Create a report to help us improve
-title: ''
-labels: ''
-assignees: ''
-
+title: ""
+labels: ""
+assignees: ""
 ---
 
 **Describe the bug**
 A clear and concise description of what the bug is.
 
 **To Reproduce**
 Steps to reproduce the behavior:
+
 1. Go to '...'
 2. Click on '....'
 3. Scroll down to '....'
@@ -24,15 +24,17 @@ A clear and concise description of what you expected to happen.
 If applicable, add screenshots to help explain your problem.
 
 **Desktop (please complete the following information):**
- - OS: [e.g. iOS]
- - Browser [e.g. chrome, safari]
- - Version [e.g. 22]
+
+- OS: [e.g. iOS]
+- Browser [e.g. chrome, safari]
+- Version [e.g. 22]
 
 **Smartphone (please complete the following information):**
- - Device: [e.g. iPhone6]
- - OS: [e.g. iOS8.1]
- - Browser [e.g. stock browser, safari]
- - Version [e.g. 22]
+
+- Device: [e.g. iPhone6]
+- OS: [e.g. iOS8.1]
+- Browser [e.g. stock browser, safari]
+- Version [e.g. 22]
 
 **Additional context**
 Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,10 +1,9 @@
 ---
 name: Feature request
 about: Suggest an idea for this project
-title: ''
-labels: ''
-assignees: ''
-
+title: ""
+labels: ""
+assignees: ""
 ---
 
 **Is your feature request related to a problem? Please describe.**

.github/pull_request_template.md

@@ -1,23 +1,23 @@
-# Thank you for contributing to Dash
+> IMPORTANT: Please do not create a Pull Request without creating an issue first.
+> **Any change needs to be discussed before proceeding.** Failure to do so may result
+> in the rejection of the pull request.
+
+## Thank you for contributing to `@dash-ui/react-layout`
 
-## Before submitting
+### Before submitting
 
 Read the [CONTRIBUTING.md](../CONTRIBUTING.md) file and confirm that you're following
 all of the guidelines
 
-> ⚠️ Please do not create a Pull Request without creating an issue first.
-> **Any change needs to be discussed before proceeding.** Failure to do so may result
-> in the rejection of the pull request.
-
-## Please provide enough information so that others can review your pull request
+### Please provide enough information so that others can review your pull request
 
 - What does this implement/fix? Explain your changes.
 - Does this close any currently open issues?
 
-## Testing
+### Testing
 
 Confirm that your pull request contains tests and that all existing tests pass.
 
-## Closing issues
+### Closing issues
 
 Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if such).

.github/workflows/release.yml

@@ -0,0 +1,68 @@
+name: release
+
+on:
+  push:
+    branches:
+      - main
+      - next
+      - alpha
+  pull_request:
+    branches:
+      - main
+      - next
+      - alpha
+
+jobs:
+  release:
+    name: 🚀 Release
+    if: "!contains(github.event.head_commit.message, '[skip ci]') && !startsWith(github.event.head_commit.message, 'chore:') && !startsWith(github.event.head_commit.message, 'style:') && !contains(github.event.pull_request.title, '[skip ci]') && !startsWith(github.event.pull_request.title, 'chore:') && !startsWith(github.event.pull_request.title, 'style:') && !startsWith(github.event.head_commit.message, 'chore(') && !startsWith(github.event.head_commit.message, 'style(') && !startsWith(github.event.pull_request.title, 'chore(') && !startsWith(github.event.pull_request.title, 'style(')"
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        node-version: [16.x]
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v2
+        with:
+          fetch-depth: 0
+      - name: Setup pnpm
+        uses: pnpm/[email protected]
+        with:
+          version: 6.14.3
+      - name: Setup Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+      - name: Cache node_modules
+        id: cache-node-modules
+        uses: actions/cache@v2
+        with:
+          path: node_modules
+          key: ${{ runner.os }}-modules-${{ hashFiles('**/pnpm-lock.yaml') }}
+      - name: Install
+        if: steps.cache-node-modules.outputs.cache-hit != 'true'
+        run: pnpm install --reporter=silent
+      - name: ✅ Check types
+        run: pnpm check-types
+      - name: 🧹 Lint
+        run: pnpm lint -- --quiet
+      - name: 🧪 Test
+        run: pnpm test -- --coverage --silent
+      - name: Publish tests to Codecov
+        if: always()
+        uses: codecov/codecov-action@v2
+        with:
+          files: coverage/clover.xml
+          verbose: false
+          fail_ci_if_error: false
+      - name: Build
+        if: "github.event_name == 'push'"
+        run: pnpm build
+      - name: Stage changes
+        if: "github.event_name == 'push'"
+        run: git add .
+      - name: 🚀 Release
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: pnpx -y semantic-release

.husky/commit-msg

@@ -0,0 +1,4 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+pnpm commitlint --edit $1

.husky/pre-commit

@@ -0,0 +1,4 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+pnpm lint-staged

.travis.yml

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

CODE_OF_CONDUCT.md

@@ -1,19 +1,15 @@
-# Contributing to Dash
+# Contributing to @dash-ui/react-layout
 
 To contribute to this project, first:
 
 1. [Fork this repo to your account](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo)
-2. ```sh
-   # Create a directory for Dash if you don't already have one
-   mkdir dash-ui
-   cd dash-ui
-   # Clone your forked repo
-   git clone https://github.com/[your-username]/react-layout.git
-   # Install the repo using Yarn
-   cd react-layout
-   yarn install
+2. [Clone this repo](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository) to your local machine
+3. ```sh
+   # Install the repo using pnpm
+   cd [repo-name]
+   pnpm install
    # Start dev mode
-   yarn dev
+   pnpm dev
    ```
 
 ## Before you contribute
@@ -29,7 +25,7 @@ Before your PR will be considered I will look for:
 
 - **Documentation** Please submit updates to the docs when public-facing APIs are changed.
 - **Tests** Your PR will not be accepted if it doesn't have well-designed tests. Additionally, make sure
-  that you run `yarn validate` before you submit your PR and make sure your PR passes the linting rules,
+  that you run `pnpm validate` before you submit your PR and make sure your PR passes the linting rules,
   type checking, and tests that already exist.
 - **Types** Your types should be as strong as possible.
 - **Comments** If your PR implements non-obvious logic, I fully expect you to explain the rationale in
@@ -38,7 +34,7 @@ Before your PR will be considered I will look for:
 
 ## Development
 
-Here's what you need to know to start developing Dash.
+Here's what you need to know to start developing `@dash-ui/react-layout`.
 
 ### Package scripts
 
@@ -62,30 +58,21 @@ Formats all of the applicable source files with prettier
 
 Runs `eslint` on the package source
 
-#### `prerelease`
-
-Runs before the package is published. This calls `validate` and `build` scripts.
-
-#### `release`
-
-Starts a release using `standard-version`. This must be run before `npm publish`.
-
 #### `test`
 
 Tests the package with `jest`
 
 #### `validate`
 
-Runs `check-types`, `lint`, and `test` scripts. This is used in CI and
-in `prerelease`.
+Runs `check-types`, `lint`, and `test` scripts.
 
 ---
 
 ### Husky hooks
 
 #### `pre-commit`
 
-Runs `lint-staged` and the `build-types` script
+Runs `lint-staged` script
 
 #### `commit-msg`