Github: Issue Formatter

[AkhileshNegi]

Summary

Issues are now automatically reformatted upon creation with improved titles and descriptions for better clarity and consistency

[coderabbitai]

Warning

Rate limit exceeded

@AkhileshNegi has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 59 minutes and 25 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 59 minutes and 25 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d6261346-d5a2-4f61-8147-1b048626a860

📥 Commits

Reviewing files that changed from the base of the PR and between 69a8155 and 8013a07.

📒 Files selected for processing (1)

• .github/workflows/issue-formatter.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch github/issue-template

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[nishika26]

there is just one issue with this and it is that no matter if the issue is a feature/enhancement/bug issue, it fits all into the feature template. this is not that big of a problem but if there is a solution for this, then maybe we consider that? or we can merge this for now and later on do enhancements accordingly

[AkhileshNegi]

yeah that crossed my mind in past, i was thinking to make kick off this only after tag and then we can be consious of what tag we put. But for now since this is first version we can keep it as it is and then update across repos