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

[doc] Move the naming-style documentation to invalid-name doc #6669

Conversation

Pierre-Sassoulas
Copy link
Member

@Pierre-Sassoulas Pierre-Sassoulas commented May 23, 2022

Type of Changes

Type
βœ“ πŸ”¨ Refactoring
βœ“ πŸ“œ Docs

Description

Same reasoning than for #6659. This is the most searched message in the documentation too, by far with double the hit of other messages, see #5953 (comment).

Copy link
Collaborator

@DanielNoord DanielNoord left a comment

Choose a reason for hiding this comment

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

Perhaps a bit long for details.rst but I agree this is better than current situation and probably also a place users will find it earlier.

@coveralls
Copy link

coveralls commented May 23, 2022

Pull Request Test Coverage Report for Build 2370688596

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 95.414%

Totals Coverage Status
Change from base Build 2369570640: 0.0%
Covered Lines: 16230
Relevant Lines: 17010

πŸ’› - Coveralls

In order for the directory to exists so pylint_options
do not need to create the directory.
@Pierre-Sassoulas Pierre-Sassoulas force-pushed the move-invalid-name-documentation branch from 1f47e52 to b3b5894 Compare May 23, 2022 10:40
@Pierre-Sassoulas Pierre-Sassoulas merged commit ef40b99 into pylint-dev:main May 23, 2022
@Pierre-Sassoulas Pierre-Sassoulas deleted the move-invalid-name-documentation branch May 23, 2022 10:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants