TLS-133-tracking-wpengine-pre-commit-terraform-via-dependabot-bump-tj-actions-changed-files-to-41

.codecov.yml

@@ -0,0 +1,50 @@
+codecov:
+  notify:
+    after_n_builds: 21  # Number of test matrix+lint jobs uploading coverage
+    wait_for_ci: false
+
+  require_ci_to_pass: false
+  # notsecret  # repo-scoped, upload-only, stability in fork PRs
+  token: >-
+    7316089b-55fe-4646-b640-78d84b79d109
+
+comment:
+  require_changes: true
+
+coverage:
+  range: 100..100
+  status:
+    patch:
+      default:
+        target: 100%
+      pytest:
+        target: 100%
+        flags:
+        - pytest
+      typing:
+        flags:
+        - MyPy
+    project:
+      default:
+        target: 95%
+      lib:
+        flags:
+        - pytest
+        paths:
+        - src/
+        target: 100%
+      tests:
+        flags:
+        - pytest
+        paths:
+        - tests/
+        target: 100%
+      typing:
+        flags:
+        - MyPy
+        target: 90%
+
+github_checks:
+  # Annotations are deprecated in Codecov because they are misleading.
+  # Ref: https://github.com/codecov/codecov-action/issues/1710
+  annotations: false

.coderabbit.yaml

@@ -0,0 +1,19 @@
+# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
+reviews:
+  # Collapse main AI comment by default, as it takes too much space when
+  # expanded. It also is needless for subsequent rounds of PR review, mostly
+  # only for the first one
+  collapse_walkthrough: true
+  # Move AI-generated summary from PR description to main AI comment. It
+  # hallucinates sometimes, especially with PRs that change code linting rules
+  high_level_summary_in_walkthrough: true
+  # Disable false-positive cross links to issues
+  related_issues: false
+  # Disable false-positive cross links to PRs
+  related_prs: false
+  # Disable useless Poem generation
+  poem: false
+
+  auto_review:
+    # Enable AI review for Draft PRs
+    drafts: true

.coveragerc

@@ -0,0 +1,34 @@
+[html]
+show_contexts = true
+skip_covered = false
+
+[paths]
+_site-packages-to-src-mapping =
+  src
+  */src
+  *\src
+  */lib/pypy*/site-packages
+  */lib/python*/site-packages
+  *\Lib\site-packages
+
+[report]
+skip_covered = true
+skip_empty = true
+show_missing = true
+exclude_also =
+  ^\s*@pytest\.mark\.xfail
+  ^\s*\.\.\.\s*(#.*)?$
+
+[run]
+branch = true
+cover_pylib = false
+# https://coverage.rtfd.io/en/latest/contexts.html#dynamic-contexts
+# dynamic_context = test_function  # conflicts with `pytest-cov` if set here
+parallel = true
+plugins =
+  covdefaults
+relative_files = true
+source =
+  .
+source_pkgs =
+  pre_commit_terraform

.dockerignore

@@ -2,3 +2,4 @@
 !.dockerignore
 !Dockerfile
 !tools/entrypoint.sh
+!tools/install/*.sh

.flake8

@@ -0,0 +1,108 @@
+[flake8]
+
+# Print the total number of errors:
+count = true
+
+# Don't even try to analyze these:
+extend-exclude =
+  # GitHub configs
+  .github,
+  # Cache files of MyPy
+  .mypy_cache,
+  # Cache files of pytest
+  .pytest_cache,
+  # Countless third-party libs in venvs
+  .tox,
+  # Occasional virtualenv dir
+  .venv,
+  # VS Code
+  .vscode,
+  # Metadata of `pip wheel` cmd is autogenerated
+  pip-wheel-metadata,
+
+# IMPORTANT: avoid using ignore option, always use extend-ignore instead
+# Completely and unconditionally ignore the following errors:
+extend-ignore =
+  # Legitimate cases, no need to "fix" these violations:
+  # D202: No blank lines allowed after function docstring, conflicts with `ruff format`
+  D202,
+  # E203: whitespace before ':', conflicts with `ruff format`
+  E203,
+  # E501: "line too long", its function is replaced by `flake8-length`
+  E501,
+  # W505: "doc line too long", its function is replaced by `flake8-length`
+  W505,
+  # I: flake8-isort is drunk + we have isort integrated into pre-commit
+  I,
+  # WPS305: "Found f string" -- nothing bad about this
+  WPS305,
+  # WPS322: "Found incorrect multi-line string" -- false-positives with
+  # attribute docstrings. Ref:
+  # https://github.com/wemake-services/wemake-python-styleguide/issues/3056
+  WPS322,
+  # WPS326: "Found implicit string concatenation" -- nothing bad about this
+  WPS326,
+  # WPS428: "Found statement that has no effect" -- false-positives with
+  # attribute docstrings. Ref:
+  # https://github.com/wemake-services/wemake-python-styleguide/issues/3056
+  WPS428,
+  # WPS462: "Wrong multiline string usage" -- false-positives with
+  # attribute docstrings. Ref:
+  # https://github.com/wemake-services/wemake-python-styleguide/issues/3056
+  WPS462,
+  # WPS300: "Forbid imports relative to the current folder" -- we use relative imports
+  WPS300,
+
+# https://wemake-python-styleguide.readthedocs.io/en/latest/pages/usage/formatter.html
+format = wemake
+
+# Let's not overcomplicate the code:
+max-complexity = 10
+
+# Accessibility/large fonts and PEP8 friendly.
+# This is being flexibly extended through the `flake8-length`:
+max-line-length = 79
+
+# Allow certain violations in certain files:
+# Please keep both sections of this list sorted, as it will be easier for others to find and add entries in the future
+per-file-ignores =
+  # The following ignores have been researched and should be considered permanent
+  # each should be preceded with an explanation of each of the error codes
+  # If other ignores are added for a specific file in the section following this,
+  # these will need to be added to that line as well.
+
+  tests/pytest/_cli_test.py:
+    # WPS431: "Forbid nested classes" -- this is a legitimate use case for tests
+    WPS431,
+    # WPS226: "Forbid the overuse of string literals" -- this is a legitimate use case for tests
+    WPS226,
+    # WPS115: "Require snake_case for naming class attributes" -- testing legitimate case, ignored in main code
+    WPS115,
+  # We will not spend time on fixing complexity in deprecated hook
+  src/pre_commit_terraform/terraform_docs_replace.py: WPS232
+
+# Count the number of occurrences of each error/warning code and print a report:
+statistics = true
+
+# ## Plugin-provided settings: ##
+
+# flake8-eradicate
+# E800:
+eradicate-whitelist-extend = isort:\s+\w+
+
+# flake8-pytest-style
+# PT001:
+pytest-fixture-no-parentheses = true
+# PT006:
+pytest-parametrize-names-type = tuple
+# PT007:
+pytest-parametrize-values-type = tuple
+pytest-parametrize-values-row-type = tuple
+# PT023:
+pytest-mark-no-parentheses = true
+
+# wemake-python-styleguide
+# WPS410: "Forbid some module-level variables" -- __all__ is a legitimate use case
+allowed-module-metadata = __all__
+
+show-source = true

.git-blame-ignore-revs

@@ -0,0 +1,70 @@
+# `git blame` master ignore list.
+#
+# This file contains a list of git hashes of revisions to be ignored
+# by `git blame`. These revisions are considered "unimportant" in
+# that they are unlikely to be what you are interested in when blaming.
+# They are typically expected to be formatting-only changes.
+#
+# It can be used for `git blame` using `--ignore-revs-file` or by
+# setting `blame.ignoreRevsFile` in the `git config`[1].
+#
+# Ignore these commits when reporting with blame. Calling
+#
+#   git blame --ignore-revs-file .git-blame-ignore-revs
+#
+# will tell `git blame` to ignore changes made by these revisions when
+# assigning blame, as if the change never happened.
+#
+# You can enable this as a default for your local repository by
+# running
+#
+#   git config blame.ignoreRevsFile .git-blame-ignore-revs
+#
+# This will probably be automatically picked by your IDE
+# (VSCode+GitLens and JetBrains products are confirmed to do this).
+#
+# Important: if you are switching to a branch without this file,
+# `git blame` will fail with an error.
+#
+# GitHub also excludes the commits listed below from its "Blame"
+# views[2][3].
+#
+# [1]: https://git-scm.com/docs/git-blame#Documentation/git-blame.txt-blameignoreRevsFile
+# [2]: https://github.blog/changelog/2022-03-24-ignore-commits-in-the-blame-view-beta/
+# [3]: https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view
+#
+# Guidelines:
+# - Only large (generally automated) reformatting or renaming PRs
+#   should be added to this list. Do not put things here just because
+#   you feel they are trivial or unimportant. If in doubt, do not put
+#   it on this list.
+# - When adding a single revision, use inline comment to link relevant
+#   issue/PR. Alternatively, paste the commit title instead.
+#   Example:
+#     d4a8b7307acc2dc8a8833ccfa65426ad28b3ffc9  # https://github.com/sanitizers/octomachinery/issues/1
+# - When adding multiple revisions (like a bulk of work over many
+#   commits), organize them in blocks. Precede each such block with a
+#   comment starting with the word "START", followed by a link to the
+#   relevant issue or PR. Add a similar comment after the last block
+#   line but use the word "END", followed by the same link.
+#   Alternatively, add or augment the link with a text motivation and
+#   description of work performed in each commit.
+#   After each individual commit in the block, add an inline comment
+#   with the commit title line.
+#   Example:
+#     # START https://github.com/sanitizers/octomachinery/issues/1
+#     6f0bd2d8a1e6cd2e794cd39976e9756e0c85ac66  # Bulk-replace smile emojis with unicorns
+#     d53974df11dbc22cbea9dc7dcbc9896c25979a27  # Replace double with single quotes
+#     ... <rest of the list>
+#     # END https://github.com/sanitizers/octomachinery/issues/1
+# - Only put full 40-character hashes on this list (not short hashes
+#   or any other revision reference).
+# - Append to the bottom of the file, regardless of the chronological
+#   order of the revisions. Revisions within blocks should be in
+#   chronological order from oldest to newest.
+# - Because you must use a hash, you need to append to this list in a
+#   follow-up PR to the actual reformatting PR that you are trying to
+#   ignore. This approach helps avoid issues with arbitrary rebases
+#   and squashes while the pull request is in progress.
+
+23928fbf8511697c915c3231977ee254bd3fa0c2  # chore(linters): Apply ruff-format

.git_archival.txt

@@ -0,0 +1,3 @@
+node: $Format:%H$
+node-date: $Format:%cI$
+describe-name: $Format:%(describe:tags=true)$

.gitattributes

@@ -0,0 +1 @@
+.git_archival.txt  export-subst