Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add codespell: workflow, config and fix typos it finds #3630

Merged
merged 10 commits into from
Nov 22, 2023

Conversation

yarikoptic
Copy link
Member

@yarikoptic yarikoptic commented Nov 16, 2023

Long time no commit from yours truly. I was introducing codespell to a good number of projects and eventually recalled fail2ban! I was afraid it would be non-trivial due to all the regexes etc, but it seems that codespell is damn robust and I needed to provide only a single workaround regex.

Before submitting your PR, please review the following checklist:

  • CHOOSE CORRECT BRANCH: if filing a bugfix/enhancement
    against certain release version, choose 0.9, 0.10 or 0.11 branch,
    for dev-edition use master branch. In principle could be against some released branch but since renamed substition to substitution decided to stick to master
  • MAKE SURE this PR doesn't break existing tests
  • KEEP PR small so it could be easily reviewed - just slightly over 50 files ;) I had larger ones.
  • AVOID making unnecessary stylistic changes in unrelated code

Closes #2595 and Closes #3558 (supersedes)

=== Do not change lines below ===
{
 "chain": [],
 "cmd": "codespell -w -i 3 -C 2 ./files/fail2ban-openrc.conf ./fail2ban/tests/fail2banclienttestcase.py",
 "exit": 0,
 "extra_inputs": [],
 "inputs": [],
 "outputs": [],
 "pwd": "."
}
^^^ Do not change lines above ^^^
Copy link
Contributor

@sebres sebres left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just as reference few related issues/PRs: #1896, #2595 and #3558

config/filter.d/postfix.conf Outdated Show resolved Hide resolved
@yarikoptic
Copy link
Member Author

Just as reference few related issues/PRs: #1896, #2595 and #3558

see -- you can't escape codespell -- it will keep hunting you down. Let's get over with it!!! ;)

I think it is just a filter for testing so should be safe to rename
=== Do not change lines below ===
{
 "chain": [],
 "cmd": "codespell -w",
 "exit": 0,
 "extra_inputs": [],
 "inputs": [],
 "outputs": [],
 "pwd": "."
}
^^^ Do not change lines above ^^^
@yarikoptic
Copy link
Member Author

Tests pass... Merge?

@sebres
Copy link
Contributor

sebres commented Nov 22, 2023

If you mean we really need it, then do that...
I already expressed my opinion to spelling (especially spell vs python) many times... However fail2ban project can probably cope with that (since its codebase is relative medium-sized and straightforward), and all the forks should solve the possible conflicts once.

@yarikoptic
Copy link
Member Author

ok, let's do it then in a good memory of Yarik so he never comes back with yet another spell'ing PR ;) I do not think there would even be that huge number of conflicts (I wonder if there is some service to give estimates on that). So By the power vested in me by God and man, I pronounce you 9fc754c and 8ef0d3c to be a merge! What Git has joined together, let no man put asunder. You may now rebase your PRs.

@yarikoptic yarikoptic merged commit 22ce0c0 into fail2ban:master Nov 22, 2023
8 checks passed
@szepeviktor szepeviktor mentioned this pull request Nov 22, 2023
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Codespell report for the "fail2ban" project
2 participants