fix: formatting errors

Signed-off-by: Zack Koppert <[email protected]>

.github/linters/.flake8

@@ -1,5 +1,5 @@
 [flake8]
 exclude = venv,.venv,.git,__pycache__
-extend-ignore = C901
+extend-ignore = C901, E203
 max-line-length = 150
 statistics = True

docs/dealing-with-large-issue-metrics.md

@@ -1,12 +1,13 @@
-# Dealing with large issue metrics markdown files
+# Dealing with large issue metrics Markdown files
 
 When working with lots of issues/pull requests/discussion results, the resulting issue_metrics.md  file can become very large. This can cause the GitHub API to return an error when trying to create an issue with the contents of the file.
 
 ```shell
 Pull request creation failed. Validation failed: Body is too long (maximum is 65536 characters)
 ```
 
-To work around this limitation, the issue-metrics action detects the issue and splits the issue_metrics.md file into smaller files. So instead of issue_metrics.md, you will get issue_metrics_0.md, issue_metrics_1.md, etc. Since we don't want the action to fail, it has been designed to have the same name as usual for the first split file (issue_metrics.md) and then append a number to the name for the subsequent split files.
+To work around this limitation, the issue-metrics action detects the issue and splits the issue_metrics.md file into smaller files. So instead of issue_metrics.md, you will get issue_metrics_0.md, issue_metrics_1.md, etc.
+Since we don't want the action to fail, it has been designed to have the same name as usual for the first split file (issue_metrics.md) and then append a number to the name for the subsequent split files.
 
 You can choose one of the following strategies to deal with the split files:
 - Create multiple issues, each with using the next split file in the sequence.