Add Megalinter for improved code quality #75
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
Member
|
Hi @grmbyrn I think we should also fix the errors before merging it. |
josecelano
requested changes
Nov 30, 2023
Member
josecelano
left a comment
josecelano
left a comment
There was a problem hiding this comment.
Fix errors before merging.
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.
This pull request reintroduces Megalinter, a comprehensive static analysis tool, to the Secure Git Guide project. Megalinter was previously used in the project but was removed during the migration to SvelteKit.
By adding Megalinter back to the project, we can improve the overall quality and security of the codebase.
Changes made in this pull request: