chore(pre-commit): line-count 500/750; warn on issue refs

[sugan0tech]

This PR updates pre-commit policies for file size and commit message issue references.

Changes

• Line count: warn above 500 lines; error above 750 lines.
• Issue reference: convert from hard error to warning when no #<num> is present.
• Case-insensitive exemptions for Merge/Revert and release/bump commits.
• Updated hook names/descriptions and documentation to match behavior.

Files

• scripts/line_count_check.sh
• scripts/require_issue_ref.sh
• .pre-commit-config.yaml
• CONTRIBUTING.md

Rationale

• Reduce friction on commits while still nudging best practices.
• Allow larger files within reason; keep a hard stop at 750+ lines.

Refs #34

[ssanumand]

@sugan0tech, while I appreciate the changes, I also think we're creating more resistance for the open source contributors with all these rules. What's your opinion?

[sugan0tech]

@sugan0tech, while I appreciate the changes, I also think we're creating more resistance for the open source contributors with all these rules. What's your opinion?

Agreed with your concerns, if we start to maintain these hygenes from the start will be feastable. and for the external contributors we have to consider them as black blox, for a genuine contributors these are the typical standards has to be followed. As with my previous experience each oss tools comes with their own set of guidelines integration multiple platform. Where as ours is all in github that's a advantage. But these remains a mandatory requiremet. Also that's why i had it as warning to a extent then it's an error for the file size case.

[sugan0tech]

If required i can make the commit issue reference can be a warning instead of a commit blocker. And with my recent talke with @venkatsp17 the EOF file validator is quite annoying, need to to make it auto apply at commit instead of doing a redo.

[venkatsp17]

Yeah, It must be auto-fixed in code editor instead of Pass check @sugan0tech.

[venkatsp17]

Apart from that I appreciate adding issue number with comment is to be mandatory and not case sensitive, Because I feel it would easy to track out commits when application scales.

[ssanumand]

@sugan0tech, I agree with you, automating fixes for these checks instead of showing warnings/errors to the user is the right approach.

If this is the case, I'm not as concerned as before. Good work guys. 👏

[MSHRISH]

Irunga da dai, Github paduchutu varan onumea purla 😭

[sugan0tech]

hile I appreciate the changes, I also think we're creating more resistance for the open source contributors with all these rules. What's your opinion?

if LGTM naah approve please.

[ssanumand]

Sorry for the delay, I'll approve the changes.

[ssanumand]

It's up to @venkatsp17 and @aslamcodes. Guys, please review and approve.