-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Conversation
Pull Request Test Coverage Report for Build 2274784795
π - 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/.*"] |
There was a problem hiding this comment.
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 ?
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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 π
There was a problem hiding this comment.
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 :-)
Type of Changes
Description
Fixes #6470.