Add MegaLinter GitHub Actions workflow #1203
Open
Conversation
This file contains 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.
Add MegaLinter GitHub Actions workflow, update
.editorconfig, and fix code style issues highlighted by linters.Most of the changes are fixing wrong indentation type (spaces instead of tabs and vice versa), and fixing indentation levels to be consistent.
To make the PR easier to review, this commit only has 14 file changes. When running the MegaLinter on this branch with
VALIDATE_ALL_CODEBASEset to true, the MegaLinter will fail and highlight all the source code files that have incorrect indentation, spaces instead of tabs, etc.If and when this PR is accepted and merged, I'll open subsequent PRs that address fixing code style issues in different segments of the repository.
My
megalinterFullbranch has all of the changes for the entire repository. When running the MegaLinter on that branch withVALIDATE_ALL_CODEBASEset to true, the MegaLinter passes. And I'm able to successfully build the project on themegalinterFullbranch withGP2040_BOARDCONFIG=Pico; I haven't tested building with any of the other configurations.