GH Action: Add Super-Linter #10466

Closed
opened 2026-01-31 02:22:19 +00:00 by claunia · 0 comments
Owner

Originally created by @WSLUser on GitHub (Sep 2, 2020).

Description of the new feature/enhancement

Add the recently released Github Super Linter https://github.com/github/super-linter for json, markdown and powershell in this repo as a GH action (it's in the GH Action Marketplace).

From their README:

The end goal of this tool:

Prevent broken code from being uploaded to the default branch (Usually master)
Help establish coding best practices across multiple languages
Build guidelines for code layout and format
Automate the process to help streamline code reviews

Proposed technical implementation details (optional)

Just add the action and choose the linters to use.

Originally created by @WSLUser on GitHub (Sep 2, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement Add the recently released Github Super Linter https://github.com/github/super-linter for json, markdown and powershell in this repo as a GH action (it's in the GH Action Marketplace). <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> From their README: > The end goal of this tool: > > Prevent broken code from being uploaded to the default branch (Usually master) > Help establish coding best practices across multiple languages > Build guidelines for code layout and format > Automate the process to help streamline code reviews # Proposed technical implementation details (optional) Just add the action and choose the linters to use. <!-- A clear and concise description of what you want to happen. -->
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#10466