Skip to content

lint: disable yamllint line-length check#14793

Open
vojtapolasek wants to merge 1 commit into
ComplianceAsCode:masterfrom
vojtapolasek:yamllint_take_two
Open

lint: disable yamllint line-length check#14793
vojtapolasek wants to merge 1 commit into
ComplianceAsCode:masterfrom
vojtapolasek:yamllint_take_two

Conversation

@vojtapolasek

Copy link
Copy Markdown
Collaborator

Description:

  • Disable the yamllint line-length check and update the developer style guide to reflect that the 99-character limit is preferred but not enforced.

Rationale:

  • YAML content in this project frequently embeds HTML tags, Jinja macros, and URLs that make strict line-length enforcement impractical. The check produces many false positives and is hard to comply with without degrading readability.

Review Hints:

  • Two files changed: .yamllint (config change) and docs/manual/developer/04_style_guide.md (documentation update).
  • The style guide still recommends 99 characters for new plain-text content — only the hard enforcement is removed.

this check is extremely hard to enforce in this repo, we push yaml to its borders with various HTML tags, Jinja macros etc
@vojtapolasek vojtapolasek added this to the 0.1.82 milestone Jun 11, 2026
@vojtapolasek vojtapolasek added Infrastructure Our content build system Documentation Update in project documentation. labels Jun 11, 2026
@openshift-ci

openshift-ci Bot commented Jun 11, 2026

Copy link
Copy Markdown

@vojtapolasek: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/4.20-images 1587e79 link true /test 4.20-images
ci/prow/4.21-images 1587e79 link true /test 4.21-images

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@Mab879 Mab879 self-assigned this Jun 11, 2026

@Mab879 Mab879 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Approving. Leaving this open for others to leave feedback.

* Have a total path length less than 250 characters
* Shall not use "smart quotes" or curved quotes
* Maximum line length should be 99 characters
* Maximum line length of 99 characters is preferred but not enforced.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This change is fine, but I might come back and do pass to make style guide wording follows RFC 2119 to make this clear for everything else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Documentation Update in project documentation. Infrastructure Our content build system

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants