Fix pipelines: [docs] Adjust Vale Doc Linter and Prettier configurations Issue

[pratik-mahalle]

What has changed?
This pull request addresses the issues with failing Vale Doc Linter and Prettier pipelines as described in Issue #2696.

• Fixed numerous spelling and style errors flagged by Vale across the documentation files.
• Corrected branch/tag references in the Prettier pipeline configuration.

---

Type of change

• Bug fix (non-breaking change which fixes an issue).

---

[keploy]

Nice Pr 😄. We currently support Unit Test Generation only for Go projects.
Stay tuned – support for more languages is coming soon! 🚀

[github-actions]

Thank you and congratulations 🎉 for opening your very first pull request in keploy

[Achanandhi-M]

Hi @pratik-mahalle, thanks for raising the PR!
I’m a bit confused about the number of files changed—especially since the issue seems to be related to a linter problem. Could you please elaborate on the changes, particularly why files like vale_styles/Google/GenderBias.yml were modified? It would help me better understand the context of the PR. Thanks!

[pratik-mahalle]

Hey @Achanandhi-M, Thank you for the review. I think, the main goal of this PR was to adjust the Vale Doc Linter and Prettier configurations to resolve the linter issues we were encountering. As part of this, I needed to update some of the custom style files, including vale_styles/Google/GenderBias.yml, to ensure they aligned with our current linting rules and addressed the specific problems flagged by Vale.

[Achanandhi-M]

I’ll get it reviewed by the team and follow up on the merge soon @pratik-mahalle

[khareyash05]

The pipelines are still failing @pratik-mahalle

[pratik-mahalle]

Hey @khareyash05 , In vale-lint-action.yml only the versioned_docs/version-2.0.0 directory is checked. Are we want to check only that folder?

[pratik-mahalle]

Let me try pushing the recent changes, if it works!

[Achanandhi-M]

The pipelines are still failing @pratik-mahalle

[pratik-mahalle]

Ok, Looks like some changes got merged in the repo due to which it is failing. I will fix it

[pratik-mahalle]

Hey @Achanandhi-M, I have fixed the errors and it shows me no errors, I hope it will work now.
Thanks!

[Achanandhi-M]

Hey @pratik-mahalle,
This is really amazing! I’ll ask my team to do a final review.

[pratik-mahalle]

I am not sure why Prettify code pipelines are failing, If you know please let me know @Achanandhi-M

[Achanandhi-M]

Hey @pratik-mahalle,

The reason the lint action failed is due to this issue: "subject must not be sentence-case, start-case, pascal-case, or upper-case [subject-case]".

In your commit, the subject line uses uppercase, which is why it’s failing.

Also, the Prettier code error seems to be related to a permission issue. Just checking—did you run the npx prettier --write '**/*.{js,md}' command before pushing?

Let me know if you need any help!

[pratik-mahalle]

Hey @pratik-mahalle,

The reason the lint action failed is due to this issue: "subject must not be sentence-case, start-case, pascal-case, or upper-case [subject-case]".

In your commit, the subject line uses uppercase, which is why it’s failing.

Also, the Prettier code error seems to be related to a permission issue. Just checking—did you run the npx prettier --write '**/*.{js,md}' command before pushing?

Let me know if you need any help!

Yeah, I run the prettier --write . and then I commit the changes, will it change anything?

[Achanandhi-M]

Sorry @pratik-mahalle , You can see again it is failing

[pratik-mahalle]

Yeah, one is failing due to permission and another one is failing due to the commit syntax I think. Can you tell me what could be the reason behind that lint-codebase pipeline failure

[pratik-mahalle]

I have update the commit message and add the required permission also, let`s check if it work or not @Achanandhi-M

[Achanandhi-M]

Sorry @pratik-mahalle,
It’s still failing. Please give me some time to figure out why. Maybe if we close this PR and create a new one with the update commits message, the commit message issues might be resolved—but I’m not entirely sure yet.

[pratik-mahalle]

Okay @Achanandhi-M , I am also figuring it out. Let me know if you find a solution.