Skip to content
This repository was archived by the owner on Aug 12, 2024. It is now read-only.

Add markdown linter GH Action#318

Merged
exdx merged 2 commits intooperator-framework:mainfrom
exdx:markdown-linter
May 5, 2022
Merged

Add markdown linter GH Action#318
exdx merged 2 commits intooperator-framework:mainfrom
exdx:markdown-linter

Conversation

@exdx
Copy link
Copy Markdown
Contributor

@exdx exdx commented May 4, 2022

This PR introduces a new GH Action specifically for linting the markdown files in the repository. It relies on the https://github.com/github/super-linter project which seems to be the most maintained GH Action for linting and specifically for markdown. It only lints markdown files and does not use any of the other linters included, since golangci-lint is used for Go code in the project.

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 4, 2022
@exdx exdx force-pushed the markdown-linter branch from b7b97f6 to 69dec8e Compare May 4, 2022 20:51
@exdx exdx marked this pull request as ready for review May 4, 2022 20:52
@exdx exdx requested a review from a team as a code owner May 4, 2022 20:52
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 4, 2022
@exdx
Copy link
Copy Markdown
Contributor Author

exdx commented May 4, 2022

I suppose we could move this under the existing sanity/lint action?

@oceanc80
Copy link
Copy Markdown
Contributor

oceanc80 commented May 4, 2022

I suppose we could move this under the existing sanity/lint action?

That seems reasonable to me.

Comment thread .github/workflows/lint.yaml Outdated
Comment thread .github/workflows/lint.yaml Outdated
@exdx exdx force-pushed the markdown-linter branch 4 times, most recently from a19f8b1 to 2d0043f Compare May 4, 2022 22:03
Comment thread .github/workflows/sanity.yaml
@timflannagan
Copy link
Copy Markdown
Member

Also: should we separate out the markdown linting violations into it's own commit?

@timflannagan timflannagan added this to the 0.4 milestone May 5, 2022
@exdx
Copy link
Copy Markdown
Contributor Author

exdx commented May 5, 2022

Also: should we separate out the markdown linting violations into it's own commit?

Yes, they should be in their own commit. I squashed everything but will try to split it out 👍

Introduce a new linter as part of the sanity check that focuses
only on linting markdown files. Having a markdown linter ensures uniform
documentation formatting and leads to higher quality documentation.

The super-linter action introduced seems like the most up-to-date and
well maintained markdown linter available as a GitHub Action.
@exdx exdx force-pushed the markdown-linter branch from 2d0043f to 5bdca01 Compare May 5, 2022 13:51
@exdx exdx merged commit a73f2a7 into operator-framework:main May 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants