Skip to content
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

docs: Update to use markdownlint compatible markdown contents #11787

Merged

Conversation

sudosubin
Copy link
Contributor

Related with #11733

Motivation

Argo Workflows project has markdownlint configuration, but many markdown documents does not respect the lint rules. (I'm currently working on markdownlint.)

Modifications

  • Updated markdown documents styles, miscs
  • I'm not sure about updating the markdown templates in .github path as well, so please check about this.
  • Next PR, I will update the generated documents to be generated well.

Verification

$ markdownlint *.md docs/CONTRIBUTING.md examples manifests sdks/CONTRIBUTING.md
(clear)

Signed-off-by: sudosubin <sudosubin@gmail.com>
Copy link
Member

@agilgur5 agilgur5 left a comment

Choose a reason for hiding this comment

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

LGTM

I'm not sure about updating the markdown templates in .github path as well, so please check about this.

That's fine, the changes are tiny and make sense. There is just going to be a visible disable comment, but nbd.

Next PR, I will update the generated documents to be generated well.

Are you planning to also change the Makefile to run markdownlint on these files?

@agilgur5 agilgur5 added the area/docs Incorrect, missing, or mistakes in docs label Sep 9, 2023
@sudosubin
Copy link
Contributor Author

Are you planning to also change the Makefile to run markdownlint on these files?

Yes, of course. After changing the original go code (mainly the comments), codegen script, and openapi/json schema files, I will also update the Makefile. 👍

@terrytangyuan terrytangyuan merged commit 6bb5868 into argoproj:master Sep 11, 2023
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docs Incorrect, missing, or mistakes in docs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants