Thank you for your interest in contributing to the Aegis RWA Protocol! We are building institutional-grade infrastructure on Stellar, and community contributions are vital to our success.
The following is a set of guidelines for contributing to the Aegis RWA organization and its repositories.
If you need help, have a question, or want to discuss an architectural change before coding, please:
- Review our SUPPORT.md file.
- Join the Stellar Developer Discord and tag the Aegis team.
We use a structured branching model. Please name your branches using the following conventions:
feat/your-feature-name: For new features or significant additions.fix/issue-description: For bug fixes.chore/maintenance-task: For dependency updates, documentation changes, or internal refactoring.test/what-you-are-testing: For adding missing tests or CI improvements.
To ensure a smooth review process, please adhere to the following standards when submitting a Pull Request (PR):
- Atomic Commits: Keep your commits focused on a single logical change.
- Descriptive Titles: Use conventional commit formatting for your PR title (e.g.,
feat(contracts): implement batch whitelisting). - Link Issues: Reference the issue your PR resolves in the description (e.g.,
Closes #42). - Tests: If you are modifying Rust contracts or the TS SDK, you must include accompanying unit tests. PRs without tests will not be merged.
- CI Checks: Ensure all GitHub Actions (linting, tests, build) pass before requesting a review.
All submissions, including those from core team members, require review.
- We aim to review all PRs within 48-72 hours.
- Maintainers may ask for architectural changes or additional tests. Please respond to feedback promptly.
- Once approved by at least one core maintainer, your PR will be squash-merged into the
mainbranch.
Thank you for helping us build the future of Real-World Assets on Stellar!