Open rexagod opened 4 months ago
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rexagod
The full list of commands accepted by this bot can be found here.
The pull request process is described here
We already have https://github.com/DavidAnson/markdownlint-cli2 integration, why do we need another markdown formatter/linter?
markdownlint-cli2
wasn't able to lint the compatibility matrix, owing to which the padding logic would differ before and after the substitution or insertions were performed there. So running a linter that ensured an overall consistent README.md
format would ensure no merge conflicts happen owing to matrix padding.
/assign @CatherineF-dev /triage accepted
markdownlint-cli2
wasn't able to lint the compatibility matrix, owing to which the padding logic would differ before and after the substitution or insertions were performed there. So running a linter that ensured an overall consistentREADME.md
format would ensure no merge conflicts happen owing to matrix padding.
My preference would be a README.md.tpl doc that is authoritative to generate the README.md + a config file, see https://docs.gomplate.ca/usage/ for example.
PR needs rebase.
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the PR is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
To primarily avoid conflicts and allow for automations.