Repository navigation
CONTRIBUTING.md — contribution workflow and branch policy #540
Description
Write CONTRIBUTING.md at the repo root. Cover: forking and branching, the required dev base branch, commit message conventions (Conventional Commits — feat:, fix:, docs:, with scopes like feat(backend):), how to link an issue so close-linked-issues.yml closes it on merge, the PR template, and which CI checks must pass before review.
Acceptance criteria:
- States prominently and early that PRs must target
dev, and that PRs tomainare auto-closed byguard-main-branch.ymlwith a bot comment - Explains that the auto-close is not a rejection of the work — the contributor reopens against
dev - Documents the commit convention actually used in this repo's history, with examples
- Explains the
Closes #Nkeyword behaviour and howclose-linked-issues.ymlhandles it fordevmerges - Lists the CI jobs a PR must pass, per touched area (backend / web / ai_agent / contracts)
- Cross-linked from
README.md
Activity
Riel101 commentedon Aug 27, 2026
@Riel101 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Riel101 to this issue.
eischideraa-unn commentedon Aug 29, 2026
@eischideraa-unn has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @eischideraa-unn to this issue.
Oluwatomilola commentedon Sep 23, 2026
@Oluwatomilola has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Oluwatomilola to this issue.
Damola09 commentedon Sep 28, 2026
@Damola09 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Damola09 to this issue.
drips-wave commentedon Sep 28, 2026
Congratulations, @Damola09! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @Damola09: 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 🌊
docs: document group_treasury storage/multisig, local object store, a…
github-actions commentedon Sep 29, 2026
Closed by #611, merged into
dev.drips-wave commentedon Sep 29, 2026
This issue has been completed by @Damola09 as part of the Stellar Wave Program's 9th Wave 🥳
😎 @Damola09: 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.