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

Fixing typos in too-many-branches example #9486

Conversation

fortin-alex
Copy link
Contributor

Type of Changes

Type
πŸ› Bug fix
✨ New feature
πŸ”¨ Refactoring
βœ“ πŸ“œ Docs

Description

Refs #XXXX

Closes #9485

In this PR, we fix 2 typos that are appearing in the too-many-branches / R0912 documentation of pylint

@Pierre-Sassoulas Pierre-Sassoulas added Documentation πŸ“— Skip news πŸ”‡ This change does not require a changelog entry labels Mar 6, 2024
@Pierre-Sassoulas Pierre-Sassoulas enabled auto-merge (squash) March 6, 2024 20:15
@Pierre-Sassoulas
Copy link
Member

Thank you :)

Copy link

codecov bot commented Mar 6, 2024

Codecov Report

All modified and coverable lines are covered by tests βœ…

Project coverage is 95.82%. Comparing base (6a09d29) to head (2e180ea).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #9486   +/-   ##
=======================================
  Coverage   95.82%   95.82%           
=======================================
  Files         173      173           
  Lines       18797    18797           
=======================================
+ Hits        18012    18013    +1     
+ Misses        785      784    -1     

see 1 file with indirect coverage changes

@Pierre-Sassoulas Pierre-Sassoulas merged commit 0d120a5 into pylint-dev:main Mar 6, 2024
29 of 30 checks passed
@fortin-alex fortin-alex deleted the Fixing-typos-in-too-many-branches-examples branch March 6, 2024 21:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation πŸ“— Skip news πŸ”‡ This change does not require a changelog entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Documentation] - Fix 2 typos in too-many-branches documentation
3 participants