How We Review and Validate PRAXIST Contributions

[electrixoul]

We’re still learning how to maintain and evolve PRAXIST responsibly, and we’ve established the following contribution workflow:

1. Submit an issue or PR
2. Maintainers review it, and proposed fixes move into validation branches
3. Related PRs may be grouped into a focused validation branch
4. Each branch goes through CI and real-world task testing, typically requiring 1–3 days of validation by the PRAXIST maintenance team
5. Once validated, changes are merged into main, validation branches are removed, and contributors are credited

We aim to run this cycle on a weekly basis. We’re grateful for every piece of feedback, idea, and contribution that helps make PRAXIST better.
More updates are coming soon. Stay tuned.

🔗 Learn more about the contribution workflow:
https://github.com/sapientinc/PRAXIST?tab=contributing-ov-file#what-happens-after-submission

Have feedback, questions, or ideas for PRAXIST? Join our Discord community to discuss directly with the team and other builders. We’d love to hear what you’re working on—and what you’d like to see next. https://discord.gg/dX8WSFHnvj