Skip to content

Add a Git tagging policy for TeachLink Backend #1839

Closed

Description

@RUKAYAT-CODER

Background

The Governance/ folder does not yet include a Governance/policies/TAGGING.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/TAGGING.md and document the tag naming convention.
  • Specify who may tag.
  • Define the signing requirement.
  • 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

  1. shobhamerabacha-star commented on Oct 13, 2026

    @shobhamerabacha-star

    Greetings,

    I looked into the details for "Add a Git tagging policy for TeachLink Backend" and would like to contribute the fix.

    Technical Implementation Outline:

    1. Audit route handlers, DTO validation schemas, and database transaction boundaries.
    2. Implement resilient controller/service logic with idempotency and typed error handling.
    3. Add comprehensive API unit and integration tests.
    4. Verify database queries and schema integrity remain optimal.

    Please assign this issue to me. I will submit a clean, well-tested, and production-ready PR promptly!

  2. Emoji-dot commented on Oct 16, 2026

    @Emoji-dot
    Contributor

    @Emoji-dot has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    I would like to work on this issue

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

  3. eriifeomoniyi-hue commented on Oct 16, 2026

    @eriifeomoniyi-hue
    Contributor

    @eriifeomoniyi-hue has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    I love to work on this issue

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

  4. Johnsource-hub commented on Oct 16, 2026

    @Johnsource-hub
    Contributor

    @Johnsource-hub has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Please Maintainer, assign this issue to me. Thank you so much

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

  5. oladev2026-tech commented on Oct 16, 2026

    @oladev2026-tech
    Contributor

    @oladev2026-tech has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hi maintainer, can i work on this task?

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

  6. Nimatstar commented on Oct 16, 2026

    @Nimatstar
    Contributor

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

    Hi am a full stack developer, i build solutions that are scalable and maintainable. Kindly assign this to me

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

  7. drips-wave commented on Oct 16, 2026

    @drips-wave

    Congratulations, @Emoji-dot! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

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

  8. grantfox-oss commented on Oct 17, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @Emoji-dot's PR #1909 was approved and merged by @RUKAYAT-CODER.

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

    👏 Great work, @Emoji-dot! Keep contributing to rinafcode.

  9. drips-wave commented on Oct 17, 2026

    @drips-wave

    This issue has been completed by @Emoji-dot as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @Emoji-dot: 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programgovernanceProject governance: policies, roles, processespolicyA governance policy documentpriority: lowLow priority

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions