fix: pull_request_template.md does not remind authors to link the Closes #issue_id per Guidelines

[misrasamuelisiguzor-oss]

Description

Every Stellar Wave issue's Guidelines section requires 'PR description must include: Closes #[issue_id]', but it's worth confirming .github/pull_request_template.md actually includes this reminder as a checklist item, rather than relying on each contributor to remember it from the issue body alone.

This is repository-level tooling, configuration, or process rather than application code, but that doesn't make it lower stakes: onboarding friction, unclear ownership, and process gaps are consistently what determines whether a project with this much surface area (two contract trees, two backend trees, two frontend apps, a static dashboard, and an active external contributor program) stays maintainable as it grows or slowly accumulates inconsistency that nobody has the full context to untangle.

Given that this repository is actively recruiting outside contributors through the Stellar Wave bounty program (this issue included), the quality of its repository-level scaffolding, from CONTRIBUTING.md to CODEOWNERS to its issue and PR templates, has a direct and measurable effect on how many contributors are able to land a change successfully on their first attempt versus giving up in the setup phase.

Requirements and context

• Add a checklist item to the PR template reminding authors to include Closes #<issue>

Suggested execution

1. Fork the repo and create a branch

   git checkout -b fix/pr-template-closes-reminder
   

2. Implement changes

• Update .github/pull_request_template.md

3. Test and commit

• Open a test PR and confirm the template renders the reminder

Example commit message

fix: add Closes #issue reminder checklist to PR template

Guidelines

• Assignment required before starting
• PR description must include: Closes #[issue_id]
• Keep PR description professional and detailed

[Joshua-echu]

@Joshua-echu has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I've reviewed the issue thoroughly and can start working on it right away. Looking forward to contributing

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Joshua-echu to this issue.

[Awwal-dev34]

@Awwal-dev34 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello, I’d like to contribute to this issue and would appreciate the opportunity to work on it. Thank you.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Awwal-dev34 to this issue.

[Escelit]

@Escelit has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’d like to work on this issue because it addresses an important area of the project and presents a great opportunity to make a meaningful contribution. I’m particularly interested in delivering a solution that is reliable, maintainable, and aligned with the project’s existing architecture and development standards.

I have experience working across software development, including backend and frontend development, APIs, databases, testing, DevOps, and blockchain-based applications. I’m comfortable understanding existing codebases, identifying the root cause of issues, implementing clean and scalable solutions, and writing thorough tests to prevent regressions.

My approach would be to first understand the existing implementation and project conventions, then develop the solution in a focused and incremental way. I’ll ensure the changes are well-tested, documented where necessary, and do not introduce unnecessary complexity or break existing functionality. I’m also committed to clear communication, responding to review feedback, and delivering a polished contribution that provides real value to the project.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Escelit to this issue.

[acejayl]

@acejayl has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I'll update .github/pull_request_template.md to include a clear 'Closes #[issue_id]' reminder as a checklist item, so every PR links the issue it resolves per the Stellar Wave Guidelines rather than relying on contributors to remember it. I'll place it near the top of the template with a short note on the required format and keep the existing template sections intact. I'll make sure the wording matches the Guidelines phrasing exactly. Happy to take it on.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @acejayl to this issue.

[kwest0002-lab]

@kwest0002-lab has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

please i will love to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @kwest0002-lab to this issue.

[drips-wave]

Congratulations, @kwest0002-lab! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @kwest0002-lab: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊