CREATE CUSTOM ISSUE TEMPLATE

[alo7lika]

Pull Request for PyVerse 💡

Requesting to submit a pull request to the PyVerse repository.

---

Issue Title

Please enter the title of the issue related to your pull request.
Creating a Custom Issue Template for PyVerse

• I have provided the issue title.

---

Info about the Related Issue

What's the goal of the project?
The goal of PyVerse is to create a custom issue template for the project that can significantly enhance the process of issue reporting and tracking.

• I have described the aim of the project.

---

Name

Please mention your name.
Alolika Bhowmik

• I have provided my name.

---

GitHub ID

Please mention your GitHub ID.
alo7lika

• I have provided my GitHub ID.

---

Email ID

Please mention your email ID for further communication.
[email protected]

• I have provided my email ID.

---

Identify Yourself

Mention in which program you are contributing (e.g., WoB, GSSOC, SSOC, SWOC).
GSSoC

• I have mentioned my participant role.

---

Closes

Enter the issue number that will be closed through this PR.
Closes: #1083

• I have provided the issue number.

---

Describe the Add-ons or Changes You've Made

Give a clear description of what you have added or modified.
I have added a custom issue template to the project. This template includes structured fields for issue reporting, which will help contributors provide necessary details upfront, improve clarity, and streamline issue management for maintainers.

• I have described my changes.

---

Type of Change

Select the type of change:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Code style update (formatting, local variables)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

---

How Has This Been Tested?

Describe how your changes have been tested.
I have tested the new issue template by creating sample issues in a test repository. Each field in the template appears as intended, and it effectively guides the user through structured issue reporting.

• I have described my testing process.

---

Checklist

Please confirm the following:

• My code follows the guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly wherever it was hard to understand.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have added things that prove my fix is effective or that my feature works.
• Any dependent changes have been merged and published in downstream modules.

[github-actions]

👋 Thank you for opening this pull request! We're excited to review your contribution. Please give us a moment, and we'll get back to you shortly!

Feel free to join our community on Discord to discuss more!

[alo7lika]

@UTSAVS26 the task has been completed. Kindly review the PR