feat: Updating linting tools and documentation #1349
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit updates the Markdown linting configuration files, and adds an explanation of the linting available in the repository to the process documentation. The linter itself has been used on multiple files also affected in this commit There are a handful of peripheral changes made in the PR: - Adding the latest catalogue tags to the Hugo archetype metadata - Fixing a broken link for NGINX Amplify - Fixing duplicate tabs caused by includes (Closes #1343) - Adding reload instructions to NGINX configuration (Closes #1346)
github-actions
bot
added
documentation
✅ Deploy Preview will be available once build job completes!
|
JTorreG
approved these changes
Oct 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
This commit updates the Markdown linting configuration files, and adds an explanation of the linting available in the repository to the process documentation. The linter itself has been used on multiple files also affected in this commit.
Closes #1171
There are a handful of peripheral changes made:
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩