Feature Request: Automated Formatting & Linting Workflow

[Sourya07]

Current Behavior

Currently, code formatting is not enforced automatically. This can lead to:
• Inconsistent code style across files
• Formatting-only diffs in PRs
• Extra review overhead for maintainers
• Style regressions slipping into master

Proposed Solution

->Implement Prettier with a CI-based formatting check that runs on every Pull Request.

Tooling Choice
• Formatter: Prettier
• Why Prettier?
• Supports JavaScript, CSS, HTML, Markdown, and YAML
• Minimal configuration
• Widely adopted and contributor-friendly

Verification Plan

•	Open a test PR with intentionally unformatted code → workflow should fail
•	Format the code locally using npm run format → workflow should pass
•	Ensure contributors can easily fix issues locally

Screenshots / Mockups

---

Contributor Guides and Resources

• 🎨 Wireframes and designs for Meshery UI in Figma (open invite)
• 🖥 Contributing to Meshery Website
• 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

[bhanu-agrawal]

/assign

[Sourya07]

@saurabhraghuvanshii please look up this

[Sourya07]

@saurabhraghuvanshii thanks mate

[Sourya07]

@saurabhraghuvanshii
I noticed that around 80 files have inconsistent formatting in the recent codebase.
Before proceeding, I wanted to confirm the preferred approach:
• Should I format them using Prettier (which would result in a large formatting-only diff), or
• Should I limit this PR strictly to the feature changes and handle formatting separately (or in a follow-up PR)?

[saurabhraghuvanshii]

@Sourya07 it'll good if you first format all files then we proceed with next step

[Sourya07]

@saurabhraghuvanshii can you tell me should i exclude or include .github folder for this
please confirm this .