Repository navigation
Add a merge strategy policy for TeachLink Web #1739
Description
Background
The Governance/ folder does not yet include a Governance/policies/MERGE_STRATEGY.md document. This is a governance gap: contributors and maintainers lack a clear, versioned reference for this area of governance. Adding the document closes the gap and keeps the change self-contained within the Governance folder.
Implementation Plan
- Create
Governance/policies/MERGE_STRATEGY.mdand document the allowed merge strategies. - Specify the squash and linear-history rules.
- Define the exceptions.
- Add regression tests where applicable
- Document the change
Acceptance Criteria
- Governance requirement is implemented successfully
- Scope is limited to a maximum of two files
- No changes are made outside the Governance folder
- No regression in existing functionality
- Tests pass and code follows project standards
- Change is documented
Activity
ranjeet150 commentedon Oct 13, 2026
Hello,
I am interested in taking up "Add a merge strategy policy for TeachLink Web" and implementing a production-grade solution.
Technical Implementation Outline:
Please assign this issue to me. I will submit a clean, well-tested, and production-ready PR promptly!
claire99-bit commentedon Oct 16, 2026
@claire99-bit has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @claire99-bit to this issue.
sulaimonaregbeshola commentedon Oct 16, 2026
@sulaimonaregbeshola has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @sulaimonaregbeshola to this issue.
Sagethepeak commentedon Oct 16, 2026
@Sagethepeak has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Sagethepeak to this issue.
Menjay7 commentedon Oct 16, 2026
@Menjay7 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Menjay7 to this issue.
drips-wave commentedon Oct 16, 2026
Congratulations, @Menjay7! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @Menjay7: 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 commentedon Oct 16, 2026
🎉 This issue has been marked as completed on GrantFox!
@Menjay7's PR #1795 was approved and merged by @RUKAYAT-CODER.
🏆 @Menjay7: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,527 total points). Track your full progress on GrantFox.
👏 Great work, @Menjay7! Keep contributing to rinafcode.
drips-wave commentedon Oct 16, 2026
This issue has been completed by @Menjay7 as part of the Stellar Wave Program's 10th Wave 🥳
😎 @Menjay7: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, 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.