I broke up with neovim....vim is my best friend now

dot_vim/plugged/ale/dot_github/CODE_OF_CONDUCT.md

@@ -0,0 +1,3 @@
+Codes of conduct are totally unnecessary and dumb.
+
+Just don't be a jerk and have fun.

dot_vim/plugged/ale/dot_github/CONTRIBUTING.md

@@ -0,0 +1,25 @@
+## Guidelines
+
+Have fun, and work on whatever floats your boat. Take It Easy :tm:.
+
+For help with contributing to ALE, see `:help ale-development` in Vim, or view
+the help file online [here](/doc/ale-development.txt).
+
+## Creating Issues
+
+Before creating any issues, please look through the current list of issues and
+pull requests, and ensure that the issue hasn't already been reported. If an
+issue has already been reported, but you have some new insight, please add
+a comment to the existing issue.
+
+Please read the FAQ in the README before creating any issues. A feature
+you desire may already exist and be documented, or the FAQ might explain
+how to solve a problem you have already.
+
+Please try and describe any issues reported with as much detail as you can
+provide about your Vim version, the linter you were trying to run, your
+operating system, or any other information you think might be helpful.
+
+Please describe your issue in clear, grammatically correct, and easy to
+understand English. You are more likely to see an issue resolved if others
+can understand you.

dot_vim/plugged/ale/dot_github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,6 @@
+---
+blank_issues_enabled: false
+contact_links:
+  - name: Ask for Help
+    url: https://github.com/dense-analysis/ale/discussions/new?category=q-a-ask-for-help-with-problems
+    about: Ask for Help in ALE Discussions

dot_vim/plugged/ale/dot_github/ISSUE_TEMPLATE/report-a-bug.md

@@ -0,0 +1,48 @@
+---
+name: Report a bug
+labels: bug
+about: Report a bug with ALE.
+
+---
+
+<!--
+  This is the template for reporting ALE bugs. Make sure you try updating ALE
+  to a more recent version before reporting a bug. Look through existing bug
+  reports for similar issues before reporting a new one. Don't leave comments
+  about new bugs in the comment section for old issues.
+
+  Make sure to try disabling other plugins and trying to repeat your bug before
+  reporting it in ALE. Some times problems can arise when two plugins are used
+  together, but often your issues might be problems with other plugins.
+-->
+
+## Information
+
+**VIM version**
+
+<!-- Paste just the first two lines of :version here. -->
+
+Operating System: <!-- Describe your operating system version. -->
+
+## What went wrong
+
+<!-- Describe what went wrong here. Be specific. -->
+
+Something went wrong in specifically this place, and I also searched through both open and closed issues for the same problem before reporting a bug here.
+
+Are you having trouble configuring ALE? Try asking for help on [Stack Exchange](https://vi.stackexchange.com/) or perhaps on [Reddit](https://www.reddit.com/r/vim/) instead. The GitHub issue tracker should be used for reporting bugs or asking for new features.
+
+## Reproducing the bug
+
+<!-- Write a list of steps below. -->
+
+1. I did this.
+2. Then this happened.
+
+### :ALEInfo
+<details>
+  <summary>Expand</summary>
+  <!-- Paste the output of :ALEInfo here. Try :ALEInfoToClipboard -->
+  <!-- Make sure to run :ALEInfo from the buffer where the bug occurred. -->
+  <!-- Read the output. You might figure out what went wrong yourself. -->
+</details>

dot_vim/plugged/ale/dot_github/ISSUE_TEMPLATE/suggest-a-new-linter-or-fixer.md

@@ -0,0 +1,21 @@
+---
+name: Suggest a new linter or fixer
+labels: new tool
+about: Suggest a new tool ALE can officially integrate with.
+
+---
+
+<!--
+  Write "Add support for foobar" as the issue title, or similar.
+
+  Fill out the details below.
+-->
+
+**Name:** foobar
+**URL:** https://foo.bar.com
+
+<!--
+  Write a description of the tool, and add any other information you think might
+  be helpful. Consider creating a pull request to add support for the tool
+  yourself.
+-->

dot_vim/plugged/ale/dot_github/ISSUE_TEMPLATE/suggest-an-improvement.md

@@ -0,0 +1,8 @@
+---
+name: Suggest an improvement
+labels: enhancement
+about: Suggest some way to improve ALE, or add a new feature.
+
+---
+
+<!-- There's no fixed format for feature requests. Just add your thoughts. -->

dot_vim/plugged/ale/dot_github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,13 @@
+<!--
+Before creating a pull request, do the following.
+
+* Read the Contributing guide linked above first.
+* Read the documentation that comes with ALE with `:help ale-dev`.
+
+Have fun!
+-->
+
+Where are the tests? Have you added tests? Have you updated the tests? Read the
+comment above and the documentation referenced in it first. Write tests!
+
+Seriously, read `:help ale-dev` and write tests.

dot_vim/plugged/ale/dot_github/stale.yml

@@ -0,0 +1,17 @@
+---
+# This configuration closes stale PRs after 56 + 7 days.
+# That's 8 weeks until stale bot complains, and a week until it closes a PR.
+# Issues in ALE are never, ever stale. They are either resolved or not.
+only: pulls
+daysUntilStale: 56
+daysUntilClose: 7
+exemptLabels: []
+staleLabel: stale
+markComment: >
+  This pull request has been automatically marked as stale because it has not
+  been updated recently. Make sure to write tests and document your changes.
+  See `:help ale-dev` for information on writing tests.
+
+  If your pull request is good to merge, bother w0rp or another maintainer
+  again, and get them to merge it.
+closeComment: false

dot_vim/plugged/ale/dot_github/workflows/main.yml

@@ -0,0 +1,37 @@
+---
+name: CI
+on:  # yamllint disable-line rule:truthy
+  push:
+    branches: [ master ]  # yamllint disable-line rule:brackets
+    tags:
+      - v[0-9]+.[0-9]+.x
+      - v[0-9]+.[0-9]+.[0-9]+
+  pull_request:
+    branches: [ master ]  # yamllint disable-line rule:brackets
+
+jobs:
+  build_image:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: Build docker run image
+        shell: bash
+        env:
+          DOCKER_HUB_USER: ${{ secrets.DOCKER_HUB_USER }}
+          DOCKER_HUB_PASS: ${{ secrets.DOCKER_HUB_PASS }}
+        run: ./run-tests --build-image
+  test_ale:
+    needs: build_image
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        vim-version:
+          - '--vim-80-only'
+          - '--vim-90-only'
+          - '--neovim-02-only'
+          - '--neovim-08-only'
+          - '--linters-only'
+    steps:
+      - uses: actions/checkout@v2
+      - name: Run tests
+        run: ./run-tests -v ${{ matrix.vim-version }}