Implement standardized Pull Request Template for Polyglot Stack #106
Description
📝 Description
As MicroAI Paygate transitions to a distributed Go/Rust microservices architecture, the complexity for contributors has increased. Currently, the repository lacks a formal Pull Request (PR) Template, leading to inconsistent PR descriptions and a lack of verification for cross-service testing (e.g., ensuring a Go change doesn't break the Rust Verifier).
🎯 Proposed Solution
Create a .github/pull_request_template.md file that guides contributors through a mandatory checklist specifically tailored for this polyglot stack.
The template will include:
- Service Scope: Identification of which microservice is affected (Gateway, Verifier, or Frontend).
- Performance Impact: A prompt to confirm if the change affects the 15ms P99 latency target.
- Cryptographic Check: Verification if changes affect EIP-712 signing or k256 recovery logic.
- Testing Matrix: Checkboxes for Go unit tests, Rust unit tests, and E2E stack testing.
💎 Why this is important for MicroAI Paygate:
- Consistent Reviews: Helps maintainers immediately see which parts of the distributed system are being modified.
- Reliability: Enforces the "Request -> Challenge -> Sign -> Verify" E2E test flow for every contribution.
- Onboarding: Provides a clear path for SWOC contributors to follow, reducing friction during the review process.
✅ Tasks
- Create
.github/directory if not present. - Implement
pull_request_template.mdwith sections for "Service Scope" and "Security Impact". - Add a visual/demo section for UI/Frontend changes.
I am a contributor from SWOC'26. I would love to work on this issue and standardize our contribution workflow!
SWOC'26, SWOC