Skip to content

Allow not yet published extensions links in linkcheck #6499

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

Merged
merged 1 commit into from
May 5, 2022

Conversation

DanielNoord
Copy link
Collaborator

  • Add yourself to CONTRIBUTORS if you are a new contributor.
  • Write a good description on what the PR does.

Type of Changes

Type
βœ“ πŸ”¨ Refactoring

Description

Fixes #6470.

@DanielNoord DanielNoord added Documentation πŸ“— Maintenance Discussion or action around maintaining pylint or the dev workflow labels May 5, 2022
@DanielNoord DanielNoord added this to the 2.14.0 milestone May 5, 2022
@coveralls
Copy link

Pull Request Test Coverage Report for Build 2274784795

  • 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.187%

Totals Coverage Status
Change from base Build 2272507527: 0.0%
Covered Lines: 15900
Relevant Lines: 16704

πŸ’› - Coveralls

@@ -241,3 +241,5 @@
# Prevent label issues due to colliding section names
# through including multiple documents
autosectionlabel_prefix_document = True

linkcheck_ignore = ["https://github.com/PyCQA/pylint/blob/main/pylint/extensions/.*"]
Copy link
Member

Choose a reason for hiding this comment

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

Could we check the extension on main (where the extension should be published already) but not on feature branch by creating a CI job specific for this test ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yeah, but then we're likely to miss failures on the step right? I don't think these links will ever break, so it should be fine to just ignore these very specific links in normal CI runs?

Copy link
Member

Choose a reason for hiding this comment

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

Well, 2 weeks ago we did not check ANY links, I think we'll be fine πŸ˜„

Copy link
Member

Choose a reason for hiding this comment

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

All the choices are somewhat flawed :-)

@Pierre-Sassoulas Pierre-Sassoulas merged commit 0a4204f into pylint-dev:main May 5, 2022
@DanielNoord DanielNoord deleted the doclinks branch May 5, 2022 12:19
@Pierre-Sassoulas Pierre-Sassoulas removed this from the 2.14.0 milestone May 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation πŸ“— Maintenance Discussion or action around maintaining pylint or the dev workflow
Projects
None yet
Development

Successfully merging this pull request may close these issues.

PRs creating extensions will always fail the documentation check
4 participants