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

Fix markdownlint in site #1499

Merged
merged 2 commits into from
Jan 24, 2024
Merged

Fix markdownlint in site #1499

merged 2 commits into from
Jan 24, 2024

Conversation

lucacome
Copy link
Member

@lucacome lucacome commented Jan 23, 2024

Proposed changes

Problem: The configuration for the site directory didn't have a standard name and wasn't getting picked up by markdownlint-cli. The Makefile was also referencing .markdownlint.yaml that doesn't exist.

Also the configuration for .pre-commit-config.yaml was invalid and the autoupdate wasn't working correctly.

Solution: Change the name of the configuration to a standard one that can be used automatically be the tool.
Update pre-commit config and Makefile and run the linter to fix the existing problems.

Checklist

Before creating a PR, run through this checklist and mark each as complete.

  • I have read the CONTRIBUTING doc
  • I have added tests that prove my fix is effective or that my feature works
  • I have checked that all unit tests pass after adding my changes
  • I have updated necessary documentation
  • I have rebased my branch onto main
  • I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

@lucacome lucacome requested review from a team as code owners January 23, 2024 20:19
@github-actions github-actions bot added documentation Improvements or additions to documentation chore Pull requests for routine tasks labels Jan 23, 2024
Problem: The configuration for the `site` directory didn't have a
standard name and wasn't getting picked up by markdownlint-cli. The
Makefile was also referencing .markdownlint.yaml that doesn't exist.

Also the configuration for .pre-commit-config.yaml was invalid and the
autoupdate wasn't working correctly.

Solution: Change the name of the configuration to a standard one that
can be used automatically be the tool.
Update pre-commit config and Makefile and run the linter to fix the
existing problems.
Copy link
Contributor

@kate-osborn kate-osborn left a comment

Choose a reason for hiding this comment

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

LGTM. Do we need @nginxinc/nginx-docs to sign off?

@ADubhlaoich
Copy link
Contributor

LGTM. Do we need @nginxinc/nginx-docs to sign off?

Definitely not IMO. There's a lot about that Makefile that is non-functional in my opinion: Vale isn't currently used/enforced, for example.

Hack at anything pipeline related until it works the way you want it to, we'll prioritise merging improvements at a later point.

Copy link
Contributor

@ADubhlaoich ADubhlaoich left a comment

Choose a reason for hiding this comment

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

Approving for posterity.

@lucacome lucacome merged commit 4f2b499 into nginxinc:main Jan 24, 2024
27 checks passed
@lucacome lucacome deleted the chore/markdown branch January 24, 2024 17:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Pull requests for routine tasks documentation Improvements or additions to documentation
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants