feat: Add Prettier formatting workflow

[Sourya07]

Description
This PR introduces automated code formatting using Prettier to ensure consistent code style across the repository.

This PR fixes #2534
Have two command ->

npm run lint
npm run format

How it works

1. When a PR is opened, the GitHub Action runs prettier --check .
2. If any file is unformatted, the Action fails
3. Contributors run npm run format locally to fix formatting
4. Push the fixed files and the Action passes

Testing

• npm run lint passes locally
• Verified formatting changes don't affect functionality
• Jekyll site builds successfully

Notes for Reviewers

Signed commits

• Yes, I signed my commits.

[netlify]

✅ Deploy Preview for mesheryio-preview ready!

Name	Link
🔨 Latest commit	c9355bd
🔍 Latest deploy log	https://app.netlify.com/projects/mesheryio-preview/deploys/6966a7ac63e44300086583ff
😎 Deploy Preview	https://deploy-preview-2538--mesheryio-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[gemini-code-assist]

Summary of Changes

Hello @Sourya07, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request establishes a robust code formatting standard by integrating Prettier into the development workflow. The primary goal is to maintain a uniform code style, which enhances readability and simplifies collaboration. This change streamlines the contribution process by providing clear mechanisms for style adherence and automated validation.

Highlights

• Automated Code Formatting: Introduced Prettier to automatically format code, ensuring consistent style across the repository.
• GitHub Actions Integration: A new GitHub Action runs prettier --check . on every pull request, failing if any files are unformatted to enforce style guidelines.
• Local Formatting Commands: Added npm run lint and npm run format commands for contributors to check and fix formatting locally before pushing changes.
• Prettier Configuration: Configured Prettier rules via a new .prettierrc file and specified ignored files/directories in .prettierignore.

Ignored Files

• Ignored by pattern: .github/workflows/** (10)
  • .github/workflows/add-catalog.yml
  • .github/workflows/delete-catalog.yml
  • .github/workflows/jekyll.yml
  • .github/workflows/kanvas.yml
  • .github/workflows/labeler.yml
  • .github/workflows/lint.yml
  • .github/workflows/newcomers-alert.yml
  • .github/workflows/release-drafter.yml
  • .github/workflows/tweet-label.yaml
  • .github/workflows/updateDiscussons.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces Prettier to enforce a consistent code style across the repository, which is a great step for maintainability. The changes primarily consist of formatting adjustments applied by Prettier. I've reviewed the new configuration and the resulting code changes. My feedback includes a suggestion to improve the Prettier configuration for better consistency and a minor correction in one of the data files. Overall, this is a valuable addition to the project's tooling.

[gemini-code-assist]

For better consistency across the repository, I recommend using spaces instead of tabs for indentation. While useTabs: true is set, Prettier will still use spaces for some file types like YAML, leading to a mixed indentation style. Using spaces everywhere is a more common convention and avoids rendering issues across different editors.

	"useTabs": false

[gemini-code-assist]

There's a typo in this key. It should be embedded_video.

  embedded_video: https://www.youtube.com/embed/K2gmdIlGXNo

[Sourya07]

@saurabhraghuvanshii can you please take a look here