Merged
Conversation
Member
|
Can we ignore changelog files? They are auto-generated, and I also see a few |
Contributor
Author
|
@gispada, I've excluded changelog files and |
7ad70b6 to
bd375ba
Compare
gispada
approved these changes
Jan 10, 2025
piraspierpaolo991
added a commit
that referenced
this pull request
Apr 19, 2025
* fix: avoid validate hidden field (#67) Co-authored-by: Andrea Zucca <andrea.zucca@spindox.it> * feat: added remove value on hide element (#68) Co-authored-by: Andrea Zucca <andrea.zucca@spindox.it> * chore: derivated dirty from form values (#69) Co-authored-by: Andrea Zucca <andrea.zucca@spindox.it> * docs: improve English style in README.md (#72) * chore: add basic Markdown linting config (#73) * chore: add basic Markdown linting config * fix: exclude changelogs and node_modules from md linting --------- Co-authored-by: stackhousesrl <38560213+stackhousesrl@users.noreply.github.com> Co-authored-by: Andrea Zucca <andrea.zucca@spindox.it> Co-authored-by: Riccardo Mura <49900772+cowuake@users.noreply.github.com>
piraspierpaolo991
added a commit
that referenced
this pull request
Apr 19, 2025
* fix: avoid validate hidden field (#67) Co-authored-by: Andrea Zucca <andrea.zucca@spindox.it> * feat: added remove value on hide element (#68) Co-authored-by: Andrea Zucca <andrea.zucca@spindox.it> * chore: derivated dirty from form values (#69) Co-authored-by: Andrea Zucca <andrea.zucca@spindox.it> * docs: improve English style in README.md (#72) * chore: add basic Markdown linting config (#73) * chore: add basic Markdown linting config * fix: exclude changelogs and node_modules from md linting --------- Co-authored-by: stackhousesrl <38560213+stackhousesrl@users.noreply.github.com> Co-authored-by: Andrea Zucca <andrea.zucca@spindox.it> Co-authored-by: Riccardo Mura <49900772+cowuake@users.noreply.github.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Add configuration for simplified handling of Markdown (and hence repository documentation) linting.
List of proposed changes
markdownlint-cli2markdownlint-cli2basic configurationmarkdownlint-cli2(for both linting and fixing)DavidAnson.vscode-markdownlintto the list of VSCode recommended extensions (the extension is powered by the same linting engine behindmarkdownlint-cli2!)DavidAnson.vscode-markdownlintextension is installedHow to test the changes
npm run mdlintfor a linting dry run ornpm run mdlint:fixto apply linter's suggestions. Revert the changes before proceeding to step 2.PULL_REQUEST_TEMPLATE.mdfile, missing a blank line at the beginning of the Modified packages section and including an exceeding blank line at the end), and save the file to observe the automatic changes.Modified packages
(The effects of applying the linter's suggestions have not been included in this pull request, so none of the packages have been effectively modified.)