[FEATURE] Add GitHub Pull Request Template

[rohitkumarnaidu]

Feature description

Add a standard .github/PULL_REQUEST_TEMPLATE.md to the repository.

Problem it solves

Currently, anyone submitting a Pull Request has no guidance on what context to provide. This leads to missing information (like related issue numbers or testing instructions) and causes a lot of back-and-forth communication for maintainers during review.

Proposed solution

I'd love to draft a comprehensive PR template for VishwaGuru that checks all the necessary boxes before a PR can be reviewed. Could you please assign this to me and add the ELUSOC label so I can start working on it?

Alternatives considered

We could rely on manual comments to enforce guidelines, but automating this via a template is much more robust.

Additional context

Thanks for the awesome project!

[github-actions]

👋 Hello @rohitkumarnaidu!

Thank you for opening this issue on VishwaGuru.

Issue Details:

• Title: [FEATURE] Add GitHub Pull Request Template
• Number: [FEATURE] Add GitHub Pull Request Template #947

Next Steps:

1. A maintainer will review your issue
2. The issue may be labeled for categorization
3. Additional information might be requested
4. Once triaged, work can begin!

Tips for a great issue:

• Provide clear steps to reproduce (if it's a bug)
• Include expected vs actual behavior
• Add screenshots or logs if relevant
• Mention your environment details (OS, browser, versions, etc.)

We appreciate your contribution to making VishwaGuru better! 🚀

[rohitkumarnaidu]

Hi @maintainers,

I've outlined my proposed approach for this feature below. My goal is to ensure the implementation aligns perfectly with industry best practices and makes reviewing PRs a breeze.

Proposed Implementation Plan

• Draft Comprehensive Checklist: I will include standard verification steps (e.g., "I have run linting," "I have added unit tests") so contributors self-verify their work.
• Context & Linking: I will add placeholders requiring contributors to link to related issues and provide a summary of changes.
• Testing Plan: I will include a section asking for steps on how reviewers can manually test the changes locally.

Next Steps

If this implementation strategy looks good to the team, I am ready to start working on the Pull Request immediately.

Could you please assign this issue to me and apply the ELUSOC label so I can begin? Thank you!