Tailwind CSS class consistency changes not formatted by lint

[sheikhlimon]

After making updates to ensure Tailwind CSS classes are consistent across the codebase, some files were not automatically formatted or fixed by husky because only staged files are formatted.

Problem:

• Tailwind CSS class names were updated for consistency.
• ESLint/Prettier did not auto-format all affected files.
• This causes inconsistent code style and may block CI/CD lint checks.

[github-actions]

Thanks for opening this issue! 🎉 We'll look into it as soon as possible, estimated time for response is 5–8 hrs.

Don't raise PR unless assigned to you.

In the meantime, please provide all necessary details and context to your issue — screenshots or videos of your changes help speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your issue goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Resources which can help you know more about Github 👇🏻

1. End to End GitHub Beginner Playlist: GitHub Playlist.

2. Build your GitHub Profile: GitHub Profile Optimisation.

3. GitHub Handbook for dummies: GitHub Blog for Beginners.

[Adez017]

@sheikhlimon , i appreciate you contributions however just wait before opening the PR till the issue been assigned to you . it better to work on the issue assigned and help us to keep track .

[sheikhlimon]

@sheikhlimon , i appreciate you contributions however just wait before opening the PR till the issue been assigned to you . it better to work on the issue assigned and help us to keep track .

These were the issues I was already working on. But sure

[Adez017]

@sheikhlimon , i appreciate you contributions however just wait before opening the PR till the issue been assigned to you . it better to work on the issue assigned and help us to keep track .

These were the issues I was already working on. But sure

[sheikhlimon]

@sheikhlimon , i appreciate you contributions however just wait before opening the PR till the issue been assigned to you . it better to work on the issue assigned and help us to keep track .

These were the issues I was already working on. But sure

lol #807 this is what it means. and i respect your concern but im pretty sure whoever raises the issues gets it assigned for themselves.

[Adez017]

i understand what you mean to say but just for a safer side , please wait before raising PR till the issue been assigned @sheikhlimon

[sheikhlimon]

i understand what you mean to say but just for a safer side , please till the issue been assigned @sheikhlimon

i understand your point too.. but with all due respect how hard can it be to track despite seeing the username for the person who raised the issue also the PR with the issue number explaining whats its for. again these were the issues that needed a bit of immediate attention especially #915.. just a note about myself i dont push bad code into production. My PRs speaks for themselves most of them were minor ones but few of them were majors... and the PR that wasn't merged about the github token. When more people start contributing in this project that issue will come up again that im sure of...and again your point is duly noted for the safer side...

[Adez017]

relax bro i am not complaining that you had done something wrong , its just a procedure we follow in the recodehive community . we always welcome people like you who provide quality of changes but it surely important that we all be accountable .

[github-actions]

👤 Issue assigned to @sheikhlimon.