Repository navigation
[Feature]: Github issue template #20
Description
Activity
- addedenhancementNew feature or requestNew feature or request
on Feb 24, 2026 👋 Thank you for opening a Feature Request, @SudiptaPaul-31!
Your issue has been received and is now in the triage queue.
Detail Value 📌 Issue #20 🏷️ Labels needs-triageapplied👤 Assigned to @Olowodarey @Olowodarey — a new issue has been opened and is awaiting your review.
Please keep the conversation respectful and on-topic.
Our maintainers will respond as soon as possible. 🙏This issue has been added to the Stellar Wave Program and is worth 100 Points.
🧑💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.
Warning
Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.
🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙
- addedStellar WaveIssues in the Stellar wave programIssues in the Stellar wave program
on Feb 24, 2026 @rehna-jp has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.
I’d like to work on this issue because improving the issue template will simplify the contribution process and enhance user experience.
I’m comfortable working with GitHub repositories and editing Markdown/YAML configuration files. I can review the current template setup and update it to remove the unnecessary sections while ensuring everything remains properly structured.
I’m happy to follow the project’s guidelines and submit a clean PR.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @rehna-jp to this issue.
Congratulations, @rehna-jp! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.
🧑💻 @rehna-jp: 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 issued 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 🌊
This issue has been completed by @rehna-jp as part of the Stellar Wave Program's 2nd Wave 🥳
😎 @rehna-jp: You earned 100 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
🔍 Problem Statement
Currently while creating an issue this two extra sections of proposed solution and alternatives considerations appear and Additional context and pre
submission checklist appears. As shown in the image
💡 Proposed Solution
The task is to remove this proposed solution, lternatives considerations, Additional context and pre submission checklist section to delete
🔄 Alternatives Considered
No response
📈 Expected Impact
High — Would significantly improve user experience
📎 Additional Context
No response
✔️ Pre-submission Checklist