Merge from master #546
Merged
Merge from master #546
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
./.markdownlint-cli2.yaml Warning: 13:2 [comments] missing starting space in comment Warning: 16:2 [comments] missing starting space in comment Error: 37:3 [new-line-at-end-of-file] no new line character at the end of file Error: 37:1 [trailing-spaces] trailing spaces
./.github/dependabot.yml Error: 47:34 [new-line-at-end-of-file] no new line character at the end of file
./.github/workflows/pylint.yml Warning: 1:1 [document-start] missing document start "---" Warning: 3:1 [truthy] truthy value should be one of [false, true] Error: 21:5 [indentation] wrong indentation: expected 6 but found 4 Error: 23:81 [line-length] line too long (88 > 80 characters) Error: 47:48 [new-line-at-end-of-file] no new line character at the end of file
./.github/workflows/pylint_kyu8.yml Warning: 1:1 [document-start] missing document start "---" Warning: 3:1 [truthy] truthy value should be one of [false, true] Error: 15:5 [indentation] wrong indentation: expected 6 but found 4 Error: 17:81 [line-length] line too long (88 > 80 characters) Error: 41:36 [new-line-at-end-of-file] no new line character at the end of file
./.github/workflows/pylint_kyu7.yml Error: 16:5 [indentation] wrong indentation: expected 6 but found 4 Error: 18:81 [line-length] line too long (88 > 80 characters) Error: 42:36 [new-line-at-end-of-file] no new line character at the end of file
Error: 47:43 [new-line-at-end-of-file] no new line character at the end of file
./.github/workflows/markdown_lint.yml Error: 18:5 [indentation] wrong indentation: expected 6 but found 4 Error: 23:8 [indentation] wrong indentation: expected 8 but found 7
Error: kyu_6/valid_braces/README.md:17:81 MD013/line-length Line length [Expected: 80; Actual: 88] https://github.com/DavidAnson/markdownlint/blob/v0.36.1/doc/md013.md
Merge from master
Missing module docstring
Trailing newlines
Wrong continued indentation (add 1 space).
kyu_7/valid_parentheses/solution.py:53:19: R1736: Unnecessary list index lookup, use 'char' instead (unnecessary-list-index-lookup)
kyu_7/valid_parentheses/test_valid_parentheses.py:108:25: W1309: Using an f-string that does not have any interpolated variables (f-string-without-interpolation) kyu_7/valid_parentheses/test_valid_parentheses.py:130:26: W1309: Using an f-string that does not have any interpolated variables (f-string-without-interpolation) kyu_7/valid_parentheses/test_valid_parentheses.py:132:29: W1309: Using an f-string that does not have any interpolated variables (f-string-without-interpolation) kyu_7/valid_parentheses/test_valid_parentheses.py:154:26: W1309: Using an f-string that does not have any interpolated variables (f-string-without-interpolation) kyu_7/valid_parentheses/test_valid_parentheses.py:156:29: W1309: Using an f-string that does not have any interpolated variables (f-string-without-interpolation)
************* Module kyu_7.valid_parentheses.test_valid_parentheses kyu_7/valid_parentheses/test_valid_parentheses.py:130:26: W1309: Using an f-string that does not have any interpolated variables (f-string-without-interpolation) kyu_7/valid_parentheses/test_valid_parentheses.py:154:26: W1309: Using an f-string that does not have any interpolated variables (f-string-without-interpolation)
issue (bug_risk): Fix incorrect parameter in print_log call The print_log is using test_data instead of test_str which could cause confusing log output. Should be print_log(test_data=test_str, result=result)
Valid Parentheses - Merge pull request #543 from iKostanOrg/master
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
The pull request #546 has too many files changed.
We can only review pull requests with up to 300 changed files, and this pull request has 2192.
ikostan
added a commit
that referenced
this pull request
Dec 2, 2024
pydocstyle implementation - Merge pull request #546 from iKostanOrg/master
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.