Merge pull request #204 from github/dependabot/github_actions/super-l…

…inter/super-linter-7.0.0

chore(deps): bump super-linter/super-linter from 6.8.0 to 7.0.0

.github/linters/.jscpd.json

@@ -1,7 +1,5 @@
 {
  "threshold": 25,
- "ignore": [
- "/github/workspace/test*"
- ],
+ "ignore": ["/github/workspace/test*"],
  "absolute": true
 }

.github/pull_request_template.md

@@ -1,5 +1,6 @@
 # Pull Request
-<!-- 
+
+<!--
 PR title needs to be prefixed with a conventional commit type
 (build,chore,ci,docs,feat,fix,perf,refactor,revert,style,test)
 
@@ -9,6 +10,7 @@ examples: "feat: add new logger" or "fix: remove unused imports"
 -->
 
 ## Proposed Changes
+
 <!-- Describe what the changes are and link to a GitHub Issue if one exists -->
 
 ## Readiness Checklist

.github/release-drafter.yml

@@ -1,68 +1,68 @@
 ---
-name-template: 'v$RESOLVED_VERSION'
-tag-template: 'v$RESOLVED_VERSION'
+name-template: "v$RESOLVED_VERSION"
+tag-template: "v$RESOLVED_VERSION"
 template: |
  # Changelog
  $CHANGES
 
  See details of [all code changes](https://github.com/github/evergreen/compare/$PREVIOUS_TAG...v$RESOLVED_VERSION) since previous release
 
 categories:
- - title: '🚀 Features'
+ - title: "🚀 Features"
  labels:
- - 'feature'
- - 'enhancement'
- - title: '🐛 Bug Fixes'
+ - "feature"
+ - "enhancement"
+ - title: "🐛 Bug Fixes"
  labels:
- - 'fix'
- - 'bugfix'
- - 'bug'
- - title: '🧰 Maintenance'
+ - "fix"
+ - "bugfix"
+ - "bug"
+ - title: "🧰 Maintenance"
  labels:
- - 'infrastructure'
- - 'automation'
- - 'documentation'
- - 'dependencies'
- - 'maintenance'
- - 'revert'
- - title: '🏎 Performance'
- label: 'performance'
-change-template: '- $TITLE @$AUTHOR (#$NUMBER)'
+ - "infrastructure"
+ - "automation"
+ - "documentation"
+ - "dependencies"
+ - "maintenance"
+ - "revert"
+ - title: "🏎 Performance"
+ label: "performance"
+change-template: "- $TITLE @$AUTHOR (#$NUMBER)"
 version-resolver:
  major:
  labels:
- - 'breaking'
+ - "breaking"
  minor:
  labels:
- - 'enhancement'
- - 'fix'
+ - "enhancement"
+ - "fix"
  patch:
  labels:
- - 'documentation'
- - 'maintenance'
+ - "documentation"
+ - "maintenance"
  default: patch
 autolabeler:
- - label: 'automation'
+ - label: "automation"
  title:
- - '/^(build|ci|perf|refactor|test).*/i'
- - label: 'enhancement'
+ - "/^(build|ci|perf|refactor|test).*/i"
+ - label: "enhancement"
  title:
- - '/^(style).*/i'
- - label: 'documentation'
+ - "/^(style).*/i"
+ - label: "documentation"
  title:
- - '/^(docs).*/i'
- - label: 'feature'
+ - "/^(docs).*/i"
+ - label: "feature"
  title:
- - '/^(feat).*/i'
- - label: 'fix'
+ - "/^(feat).*/i"
+ - label: "fix"
  title:
- - '/^(fix).*/i'
- - label: 'infrastructure'
+ - "/^(fix).*/i"
+ - label: "infrastructure"
  title:
- - '/^(infrastructure).*/i'
- - label: 'maintenance'
+ - "/^(infrastructure).*/i"
+ - label: "maintenance"
  title:
- - '/^(chore|maintenance).*/i'
- - label: 'revert'
+ - "/^(chore|maintenance).*/i"
+ - label: "revert"
  title:
- - '/^(revert).*/i'
+ - "/^(revert).*/i"

.github/workflows/auto-labeler.yml

@@ -4,7 +4,7 @@ name: Auto Labeler
 on:
  # pull_request_target event is required for autolabeler to support all PRs including forks
  pull_request_target:
- types: [ opened, reopened, edited, synchronize ]
+ types: [opened, reopened, edited, synchronize]
 
 permissions:
  contents: read

.github/workflows/contributors_report.yaml

@@ -3,7 +3,7 @@ name: Monthly contributor report
 on:
  workflow_dispatch:
  schedule:
- - cron: '3 2 1 * *'
+ - cron: "3 2 1 * *"
 
 permissions:
  issues: read

.github/workflows/docker-ci.yml

@@ -3,9 +3,9 @@ name: Docker Image CI
 
 on:
  push:
- branches: [ main ]
+ branches: [main]
  pull_request:
- branches: [ main ]
+ branches: [main]
 
 permissions:
  contents: read

.github/workflows/major-version-updater.yml

@@ -3,7 +3,7 @@ name: Major Version Updater
 # Whenever a new release is made, push a major version tag
 on:
  release:
- types: [ published ]
+ types: [published]
 
 permissions:
  contents: read

.github/workflows/pr-title.yml

@@ -4,7 +4,7 @@ name: "Lint PR Title"
 
 on:
  pull_request_target:
- types: [ opened, edited, edited, synchronize ]
+ types: [opened, edited, edited, synchronize]
 
 permissions:
  contents: read

.github/workflows/python-ci.yml

@@ -6,9 +6,9 @@ name: Python package
 
 on:
  push:
- branches: [ main ]
+ branches: [main]
  pull_request:
- branches: [ main ]
+ branches: [main]
 
 permissions:
  contents: read

.github/workflows/release.yml

@@ -4,8 +4,8 @@ name: Release
 on:
  workflow_dispatch:
  pull_request_target:
- types: [ closed ]
- branches: [ main ]
+ types: [closed]
+ branches: [main]
 
 permissions:
  contents: read

.github/workflows/scorecard.yml

@@ -9,9 +9,9 @@ on:
  # To guarantee Maintained check is occasionally updated. See
  # https://github.com/ossf/scorecard/blob/main/docs/checks.md#maintained
  schedule:
- - cron: '29 11 * * 6'
+ - cron: "29 11 * * 6"
  push:
- branches: [ main ]
+ branches: [main]
 
 permissions: read-all
 

.github/workflows/stale.yaml

@@ -1,7 +1,7 @@
-name: 'Close stale issues'
+name: "Close stale issues"
 on:
  schedule:
- - cron: '30 1 * * *'
+ - cron: "30 1 * * *"
 
 permissions:
  contents: read
@@ -15,8 +15,8 @@ jobs:
  steps:
  - uses: actions/stale@28ca1036281a5e5922ead5184a1bbf96e5fc984e
  with:
- stale-issue-message: 'This issue is stale because it has been open 21 days with no activity. Remove stale label or comment or this will be closed in 14 days.'
- close-issue-message: 'This issue was closed because it has been stalled for 35 days with no activity.'
+ stale-issue-message: "This issue is stale because it has been open 21 days with no activity. Remove stale label or comment or this will be closed in 14 days."
+ close-issue-message: "This issue was closed because it has been stalled for 35 days with no activity."
  days-before-stale: 21
  days-before-close: 14
  days-before-pr-close: -1

.github/workflows/super-linter.yaml

@@ -3,7 +3,7 @@ name: Lint Code Base
 
 on:
  pull_request:
- branches: [ main ]
+ branches: [main]
 
 permissions:
  contents: read
@@ -27,7 +27,7 @@ jobs:
  python -m pip install --upgrade pip
  pip install -r requirements.txt -r requirements-test.txt
  - name: Lint Code Base
- uses: super-linter/super-linter@b4515bd4ad9d0aa4681960e053916ab991bdbe96
+ uses: super-linter/super-linter@02a1172d274f021e4c70f66e23f1085eadd1064b
  env:
  DEFAULT_BRANCH: main
  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.vscode/settings.json

@@ -1,11 +1,9 @@
 {
- "python.testing.pytestArgs": [
- "."
- ],
- "python.testing.unittestEnabled": false,
- "python.testing.pytestEnabled": true,
- "[python]": {
- "editor.defaultFormatter": "ms-python.black-formatter"
- },
- "python.formatting.provider": "none"
+ "python.testing.pytestArgs": ["."],
+ "python.testing.unittestEnabled": false,
+ "python.testing.pytestEnabled": true,
+ "[python]": {
+ "editor.defaultFormatter": "ms-python.black-formatter"
+ },
+ "python.formatting.provider": "none"
 }

CONTRIBUTING.md

@@ -1,12 +1,14 @@
 <!-- markdownlint-disable MD013 -->
 <!-- omit in toc -->
+
 # Contributing to evergreen
 
 First off, thanks for taking the time to contribute! :heart:
 
 All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us project owners and smooth out the experience for all involved. The team looks forward to your contributions. :tada:
 
 <!-- omit in toc -->
+
 ## Table of Contents
 
 - [I Have a Question](#i-have-a-question)
@@ -36,6 +38,7 @@ When contributing to this project, you must agree that you have authored 100% of
 ## Reporting Bugs
 
 <!-- omit in toc -->
+
 ### Before Submitting a Bug Report
 
 A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
@@ -51,6 +54,7 @@ A good bug report shouldn't leave others needing to chase you up for more inform
 - Can you reliably reproduce the issue? And can you also reproduce it with older versions?
 
 <!-- omit in toc -->
+
 ### How Do I Submit a Good Bug Report?
 
 Please submit a bug report using our [GitHub Issues template](https://github.com/github/evergreen/issues/new?template=bug_report.yml).
@@ -60,6 +64,7 @@ Please submit a bug report using our [GitHub Issues template](https://github.com
 This section guides you through submitting an enhancement suggestion for evergreen, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
 
 <!-- omit in toc -->
+
 ### Before Submitting an Enhancement
 
 - Make sure that you are using the latest version.
@@ -68,6 +73,7 @@ This section guides you through submitting an enhancement suggestion for evergre
 - Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature or to develop the feature yourself and contribute it to the project.
 
 <!-- omit in toc -->
+
 ### How Do I Submit a Good Enhancement Suggestion?
 
 Please submit an enhancement suggestion using our [GitHub Issues template](https://github.com/github/evergreen/issues/new?template=feature_request.yml).
@@ -80,4 +86,4 @@ We are using [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.
 
 Releases are automated if a pull request is labelled with our [SemVer related labels](.github/release-drafter.yml) or with the `vuln` or `release` labels.
 
-You can also manually initiate a release you can do so through the GitHub Actions UI.  If you have permissions to do so, you can navigate to the [Actions tab](https://github.com/github/evergreen/actions/workflows/release.yml) and select the `Run workflow` button.  This will allow you to select the branch to release from and the version to release.
+You can also manually initiate a release you can do so through the GitHub Actions UI. If you have permissions to do so, you can navigate to the [Actions tab](https://github.com/github/evergreen/actions/workflows/release.yml) and select the `Run workflow` button. This will allow you to select the branch to release from and the version to release.