Contributing to Origin by Corvus
Thank you for contributing to Origin by Corvus, engineered by Quantum Tiger (Morning Bay Technology Pvt. Ltd.).
This document outlines the engineering standards, branching strategy, commit conventions, and release procedures used by our engineering team and enterprise partners.
Git Branching & Release Model
We maintain a streamlined, trunk-based branching model with a dedicated production branch:
feat/xyz ──┐
▼
[development] ────────────► [staging / integration testing]
│
▼ (pull request & approval)
[production] ────────────► [Gitea Actions Auto-Build & Multi-Arch Image Publication]
│
▼ (auto-release & tag)
[v1.0.x] ───────────► [Client Production Deployments via install.sh / install.ps1]
master(Development Branch):- Primary branch for active development, bug fixes, and feature integration.
- All feature branches (
feat/feature-name,fix/issue-description) branch from and targetmaster.
prod(Production Release Branch):- Production-ready, validated code branch.
- Pushing or merging into
prodautomatically triggers the Gitea Actions CI/CD Pipeline, which:- Builds multi-arch container images (
linux/amd64,linux/arm64). - Publishes tagged images to the Gitea Container Registry (
git.projectdefcorp.com/quantum-tiger/origin-corvus:latest). - Generates and publishes an automated Gitea Release with changelog highlights and installer checksums.
- Builds multi-arch container images (
Commit Conventions (Conventional Commits)
We follow the Conventional Commits v1.0.0 specification:
<type>(<scope>): <short imperative summary>
[optional body providing technical context]
[optional footer referencing issues: Fixes #123]
Supported Types
feat: A new feature or capability for the platform.fix: A bug fix.perf: Performance optimization or latency reduction.security: Security patch, vulnerability fix, or dependency hardening.refactor: Code restructuring without altering external behavior.docs: Documentation, technical specification, or install guide updates.chore: Maintenance, build tool updates, or CI/CD workflow modifications.
Testing & Validation Standards
Before submitting a Pull Request:
- Script Validation: Ensure shell and PowerShell installers pass syntax checks (
bash -n install.sh,bash -n entrypoint.sh). - Multi-Arch Verification: Verify container packaging builds cleanly across
linux/amd64andlinux/arm64. - Plugin Auto-Installation: Confirm that Origin Calls, Origin Boards (
focalboard), and Origin Workflows (playbooks) auto-install and enable properly upon initial boot. - No Sensitive Data: Ensure no private keys, passwords, or tokens are committed.
Pull Request Process
- Open a Pull Request targeting
master. - Fill out all sections of the Pull Request Template.
- Ensure all automated Gitea Actions CI checks pass.
- Obtain approval from at least one Codeowner specified in CODEOWNERS.
- Once merged and validated on staging, a release PR is submitted to
prodto trigger production publishing.
Enterprise Support & Security
- Security Disclosures: Please report sensitive vulnerabilities according to SECURITY.md or email security@quantumtiger.in.
- Client Support: Contact support@quantumtiger.in.