✨ initial commit

.github/code_of_conduct.md

@@ -0,0 +1,144 @@
+# Contributor Covenant Code of Conduct for Pedants
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment‑free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socioeconomic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+<!-- TOC depthFrom:2 depthTo:6 withLinks:1 updateOnSave:1 orderedList:0 -->
+
+- [Our Pledge](#our-pledge)
+- [Our Standards](#our-standards)
+- [Enforcement Responsibilities](#enforcement-responsibilities)
+- [Scope](#scope)
+- [Enforcement](#enforcement)
+- [Enforcement Guidelines](#enforcement-guidelines)
+  1. [Correction](#1-correction)
+  1. [Warning](#2-warning)
+  1. [Temporary Ban](#3-temporary-ban)
+  1. [Permanent Ban](#4-permanent-ban)
+- [Attribution](#attribution)
+
+<!-- /TOC -->
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community&nbsp;include:
+
+- Demonstrating empathy and kindness toward other&nbsp;people
+- Being respectful of differing opinions, viewpoints, and&nbsp;experiences
+- Giving and gracefully accepting constructive&nbsp;feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the&nbsp;experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall&nbsp;community
+
+Examples of unacceptable behavior&nbsp;include:
+
+- The use of sexualized language or imagery, and sexual attention or advances
+  of any&nbsp;kind
+- Trolling, insulting or derogatory comments, and personal or
+  political&nbsp;attacks
+- Public or private&nbsp;harassment
+- Publishing others’ private information, such as a physical or email address,
+  without their explicit&nbsp;permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional&nbsp;setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or&nbsp;harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for
+moderation decisions when&nbsp;appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public&nbsp;spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline&nbsp;event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement
+at&nbsp;[github@LucasLarson.net](mailto:github@LucasLarson.net). All complaints
+will be reviewed and investigated promptly and&nbsp;fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any&nbsp;incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code
+of&nbsp;Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the&nbsp;community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was&nbsp;inappropriate. A public apology may be&nbsp;requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of&nbsp;actions.
+
+**Consequence**: A warning with consequences for continued&nbsp;behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of&nbsp;time. This
+includes avoiding interactions in community spaces as well as external channels
+like social&nbsp;media. Violating these terms may lead to a temporary or
+permanent&nbsp;ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate&nbsp;behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of&nbsp;time. No public
+or private interaction with the people involved, including unsolicited
+interaction with those enforcing the Code of Conduct, is allowed during
+this&nbsp;period. Violating these terms may lead to a permanent&nbsp;ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes
+of&nbsp;individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the&nbsp;community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant,
+version&nbsp;2.0](https://contributor-covenant.org/version/2/0/code_of_conduct).
+
+Community Impact Guidelines were inspired by [Mozilla’s code of conduct
+enforcement&nbsp;ladder](https://github.com/mozilla/inclusion/blob/master/code-of-conduct-enforcement/consequence-ladder.md#readme).
+
+For answers to common questions about this code of conduct, see
+[the&nbsp;FAQ](https://contributor-covenant.org/faq). [Translations
+are&nbsp;available](https://contributor-covenant.org/translations).

.github/codeowners

@@ -0,0 +1 @@
+* @LucasLarson

.github/dependabot.yml

@@ -0,0 +1,98 @@
+---
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://git.io/help-dependabot-configuration
+
+version: 2
+updates:
+
+  # Bundler
+  - package-ecosystem: "bundler"
+    directory: "/"
+    schedule:
+      interval: "daily"
+
+  # Cargo
+  - package-ecosystem: "cargo"
+    directory: "/"
+    schedule:
+      interval: "daily"
+
+  # Composer
+  - package-ecosystem: "composer"
+    directory: "/"
+    schedule:
+      interval: "daily"
+
+  # Docker
+  - package-ecosystem: "docker"
+    directory: "/"
+    schedule:
+      interval: "daily"
+
+  # Elm
+  - package-ecosystem: "elm"
+    directory: "/"
+    schedule:
+      interval: "daily"
+
+  # git submodules
+  - package-ecosystem: "gitsubmodule"
+    directory: "/"
+    schedule:
+      interval: "daily"
+
+  # GitHub Actions
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "daily"
+
+  # Go modules
+  - package-ecosystem: "gomod"
+    directory: "/"
+    schedule:
+      interval: "daily"
+
+  # Gradle
+  - package-ecosystem: "gradle"
+    directory: "/"
+    schedule:
+      interval: "daily"
+
+  # Maven
+  - package-ecosystem: "maven"
+    directory: "/"
+    schedule:
+      interval: "daily"
+
+  # Mix
+  - package-ecosystem: "mix"
+    directory: "/"
+    schedule:
+      interval: "daily"
+
+  # npm
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "daily"
+
+  # NuGet
+  - package-ecosystem: "nuget"
+    directory: "/"
+    schedule:
+      interval: "daily"
+
+  # pip
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "daily"
+
+  # Terraform
+  - package-ecosystem: "terraform"
+    directory: "/"
+    schedule:
+      interval: "daily"

.github/funding.yml

@@ -0,0 +1,11 @@
+---
+github: LucasLarson
+patreon: lucaslarson
+open_collective: lucaslarson
+ko_fi: lucaslarson
+tidelift:  # 1 Tidelift platform-name/package-name like `npm/babel`
+community_bridge:  # 1 Community Bridge project-name like `cloud-foundry`
+liberapay: LucasLarson
+issuehunt: lucaslarson
+otechie:  # 1 Otechie username
+custom:  # ≤ 4 custom sponsorship URLs like `['link1', 'link2']`

.github/workflows/changelog.yml

@@ -0,0 +1,45 @@
+---
+name: Changelog
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    timeout-minutes: 4
+    if: "!contains(github.event.head_commit.message, '[ci skip]')"
+    steps:
+      - uses: actions/checkout@v2
+      - name: Set up Ruby
+        uses: actions/setup-ruby@v1
+        with:
+          ruby-version: 2.7.x
+      - uses: actions/cache@v2
+        with:
+          path: vendor/bundle
+          key: "${{ runner.os }}-gem-${{ hashFiles('**/Gemfile.lock') }}"
+          restore-keys: |
+            "${{ runner.os }}-gem-"
+      - name: Create local changes
+        run: |
+          gem install github_changelog_generator
+          github_changelog_generator \
+          -u "${{ github.repository_owner }}" \
+          -p "$(git rev-parse --show-toplevel | xargs basename)" \
+          -t "${{ secrets.GITHUB_TOKEN }}" \
+          --exclude-labels duplicate,question,invalid,wontfix,nodoc \
+          --output changelog.md
+      - name: Commit files
+        run: |
+          git config --local user.email "action@github.com" && \
+          git config --local user.name "GitHub" && \
+          git add --verbose --all && \
+          git commit --verbose --message '[ci skip] Updating changelog'
+      - name: Push changes
+        uses: ad-m/github-push-action@v0.6.0
+        with:
+          github_token: "${{ secrets.GITHUB_TOKEN }}"
+          branch: "${{ github.ref }}"

.github/workflows/super-linter.yml

@@ -0,0 +1,53 @@
+---
+#################################
+#################################
+## Super-Linter GitHub Actions ##
+#################################
+#################################
+name: Super-Linter
+
+#
+# Documentation:
+# https://help.github.com/en/articles/workflow-syntax-for-github-actions
+#
+
+#############################
+# Start the job on all push #
+#############################
+on:
+  push:
+  pull_request:
+    branches: [main]
+
+###############
+# Set the Job #
+###############
+jobs:
+  build:
+    # Name the Job
+    name: Lint Code Base
+    # Set the agent to run on
+    runs-on: ubuntu-latest
+
+    ##################
+    # Load all steps #
+    ##################
+    steps:
+      ##########################
+      # Checkout the code base #
+      ##########################
+      - name: Checkout Code
+        uses: actions/checkout@v2
+        with:
+          # Full history is needed to analyze changed files
+          fetch-depth: 0
+
+      ################################
+      # Run Linter against code base #
+      ################################
+      - name: Lint Code Base
+        uses: github/super-linter@v3
+        env:
+          VALIDATE_ALL_CODEBASE: false
+          DEFAULT_BRANCH: main
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/yamllint.yml

@@ -0,0 +1,31 @@
+---
+name: YAML Lint
+on:
+  # Trigger the workflow on push or pull request,
+  # but only for the main branch
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+
+jobs:
+
+  yamllint:
+    name: Lint YAML files
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v2
+      - name: YAML Lint
+        uses: ibiqlik/action-yamllint@v3
+        with:
+          strict: true
+          config_data: |
+            extends: default
+            rules:
+              truthy:
+                allowed-values: ['true', 'false', 'on']
+        env:
+          GITHUB_ACCESS_TOKEN: "${{ secrets.GITHUB_TOKEN }}"