GitHub Issue templates still missing — #120 closed without the fix landing

[abayomicornelius]

Overview

Issue #120 ("No GitHub Issue templates") is closed, but find .github -type f shows only dependabot.yml and workflows/ci.yml — no .github/ISSUE_TEMPLATE/ directory or .github/ISSUE_TEMPLATE.md exists. Given the scale and consistent structure of issues actually filed in this repo (Overview/Requirements/Acceptance Criteria/Additional Notes, visible across essentially every issue in this tracker), a template codifying that structure would meaningfully help new contributors match house style rather than relying on osmosis from reading old issues.

Requirements

Add .github/ISSUE_TEMPLATE/bug_report.md and .github/ISSUE_TEMPLATE/feature_request.md (or a config.yml-driven set) reflecting the Overview/Requirements/Acceptance Criteria structure already in wide use.

Acceptance Criteria

• .github/ISSUE_TEMPLATE/ added with at least one template
• GitHub's "New issue" flow shows the template

Additional Notes

Verified via find .github -type f (only dependabot.yml, workflows/ci.yml). Cross-reference: #120 (closed).

[rupesh-kumar-sah]

Hello team,

I can tackle GitHub Issue templates still missing — #120 closed without the fix landing. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in MergeFi/contracts
• Core Implementation: Structure Soroban contract handlers for GitHub Issue templates still missing — #120 closed without the fix landing following project idioms and storage invariants.
• Quality Assurance: Add Soroban test cases checking unauthorized invocations, edge values, and state updates.

Ready to deliver a clean, tested PR within 12–24 hours. Please assign!

[Bashibawa]

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

Hi Maintainer, I would like to work on this issue. Please assign

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

[shaarknado]

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

I would love to solve this issue for you.

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

[gbengaeben]

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

Hi maintainer

I would love to help with this! Here is the simple, clear plan:

Issue Templates: Add the missing .github/ISSUE_TEMPLATE/ directory containing structured templates for bug reports and feature requests.

Standardized Sections: Codify the familiar Overview, Requirements, and Acceptance Criteria format to help contributors easily match the repo's style.

GitHub Integration: Ensure the new templates appear seamlessly in the platform's "New issue" selection flow.

Could you please assign this to me?

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

[unlimitedengineer]

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

I can add a focused escrow initialization test that sets the treasury to the contract’s own address and verifies it is rejected with Error::InvalidTreasury. I’ll follow the existing test setup pattern and run cargo test --workspace to ensure the full suite passes.

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

[drips-wave]

Congratulations, @unlimitedengineer! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

🧑‍💻 @unlimitedengineer: 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 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@unlimitedengineer's PR #410 was approved and merged by @chonilius.

🏆 @unlimitedengineer: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,246 total points). Track your full progress on GrantFox.

👏 Great work, @unlimitedengineer! Keep contributing to MergeFi.

[drips-wave]

This issue has been completed by @unlimitedengineer as part of the Stellar Wave Program's 9th Wave 🥳

😎 @unlimitedengineer: You earned 200 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.