iamHrithikRaj Pull request
Before opening
- Confirm the change is complete and scoped to one coherent purpose.
- Review the diff for accidental files, generated output, secrets, and unrelated cleanup.
- Rebase onto the latest target branch when repository workflow requires it.
- Run the smallest meaningful build, tests, and static validation.
- Verify the exact user-visible or operational outcome.
Title
Follow repository conventions. Prefer a short title that states what changed, not how the change was produced.
Description
Use:
Problem
Explain the failure, limitation, or need and why it matters.
Solution
Explain the behavioral change, important design decisions, and intentionally unchanged behavior.
Validation
List the concrete commands, tests, measurements, or manual scenarios that establish confidence.
Add risk, rollout, rollback, screenshots, or AI-contribution notes only when they are relevant or required.
Review lifecycle
- Open a real pull request unless the work is genuinely incomplete.
- Respond to current feedback rather than stale comments.
- Treat automated findings as hypotheses and verify them against the source.
- Fix legitimate issues with focused changes.
- Explain false positives with evidence.
- Re-run affected validation after every material correction.