Gitea Repository Features & Platform Administration
Origin by Corvus - Enterprise Code Governance, DevOps & Collaboration Architecture Quantum Tiger (Morning Bay Technology Pvt. Ltd.)
1. Executive Summary & Repository Platform
Origin by Corvus operates on a private, self-hosted Gitea instance at https://git.projectdefcorp.com/Quantum-Tiger/Origin-By-Corvus. Gitea delivers a sovereign, high-performance Git forge that completely replaces external commercial platforms while maintaining complete data sovereignty and strict operational security.
The repository leverages all nine core functional tabs (repository units) in Gitea, fully configured with enterprise automation, branch protection, structured templates, and continuous delivery pipelines:
| Tab | Description |
|---|---|
<> Code | Primary source tree browser, version history tracker, and branch governance control center |
(·) Issues | Centralized tracking for software defects, capability requests, security disclosures, and client deployment support |
⇅ Pull Requests | Enterprise code review, automated verification, and merge governance engine |
Actions | Continuous integration, continuous delivery, and operational automation engine |
Packages | Integrated, sovereign OCI and Docker Container Registry |
Projects | Kanban-style project tracking and agile sprint board management |
Releases | Official release distribution portal for versioned binaries, container digests, and changelogs |
Wiki | Internal engineering knowledge base, architecture repository, and operational runbook portal |
Activity | Real-time repository pulse, code churn audit, and team velocity dashboard |
2. In-Depth Guide: All Nine Gitea Tabs & Subsystems
Tab 1: Code (<> Code)
The primary source tree browser, version history tracker, and branch governance control center.
Key Capabilities & How to Use:
- Source Code Navigation & Web Viewer:
- Browse files across directory hierarchies with syntax highlighting for Go, TypeScript, SCSS, Bash, PowerShell, Dockerfile, and YAML.
- Use the Blame view to inspect line-by-line author attribution and historical commit context.
- Use the History view to review chronological revisions of any file or directory.
- Branch Architecture & Switching:
main(Production-Ready Trunk): Primary stable branch containing tested, production-ready code. Direct pushing is restricted by branch protection rules.production(Release Mirror Trunk): Tracks tagged client releases (v1.0.0, etc.). Kept in sync with production deployments.development(Integration Trunk): Staging branch for pre-release features and integration validation.
- Branch Protection Enforcement:
- Configured via .gitea/branch_protection.yaml and .gitea/scripts/setup_branch_protection.py.
- Force pushes are permanently disabled across all protected branches.
- Minimum 1 approving review required before pull request merges.
- Code Owner approvals enforced for sensitive directories (
.gitea/,install.sh,install.ps1,Dockerfile).
- Code Ownership (.gitea/CODEOWNERS):
- Automatically assigns reviewer teams based on modified file paths:
@Quantum-Tiger/devops: Installers, Dockerfiles, Gitea Actions workflows.@Quantum-Tiger/backend-engineers:/serverGo backend and database layers.@Quantum-Tiger/frontend-engineers:/webappReact/TypeScript interface and themes.@Quantum-Tiger/tech-docs: Documentation and architecture guides.
- Automatically assigns reviewer teams based on modified file paths:
- Cloning & Transport Protocols:
- HTTPS Clone URL:
https://git.projectdefcorp.com/Quantum-Tiger/Origin-By-Corvus.git - SSH Clone URL:
git@git.projectdefcorp.com:Quantum-Tiger/Origin-By-Corvus.git - Authentication via Personal Access Token (
GITEA_PAT) or registered SSH public keys.
- HTTPS Clone URL:
Tab 2: Issues ((·) Issues)
The centralized tracking system for software defects, capability requests, security disclosures, and client deployment support.
Key Capabilities & How to Use:
- Structured Issue Templates (.gitea/ISSUE_TEMPLATE/):
When creating a new issue, contributors choose from specialized YAML forms:
- Bug Report (
bug_report.yaml): Captures reproduction steps, expected behavior, logs, client OS, browser version, and severity. - Feature Request (
feature_request.yaml): Captures enterprise use cases, business rationale, proposed API design, and acceptance criteria. - Documentation Issue (
documentation_issue.yaml): Tracks documentation typos, broken links, missing runbooks, or API reference updates. - Security Vulnerability (
security_vulnerability.yaml): High-priority confidential reporting path for security defects and CVE assessments. - Deployment Support (
deployment_support.yaml): Bare-metal, Docker, and Coolify host deployment assistance and environment triage.
- Bug Report (
- Standard 32-Label Taxonomy (.gitea/labels.yaml):
Every issue is classified across five dimensions:
- Type (
type/*):bug,feature,security,documentation,performance,refactor,compliance. - Priority (
priority/*):priority/critical(P0 Blocker, <1 hour response SLA).priority/high(P1 Urgent, <4 hours response SLA).priority/medium(P2 Standard, sprint cycle SLA).priority/low(P3 Minor, next release SLA).
- Component (
component/*):installer,server,webapp,calls,boards,workflows,security,devops,docs. - Status (
status/*):triage,in-progress,blocked,ready-for-review,verified,resolved,duplicate,wontfix. - Release SemVer Impact (
release/*):patch,minor,major,breaking-change.
- Type (
- Milestone Tracking:
- Link issues directly to active roadmaps (
v1.0.0,v1.1.0,v1.2.0,v2.0.0) to track sprint burndown and completion percentages.
- Link issues directly to active roadmaps (
- Time Tracking & Estimation:
- Log estimated time using
/estimate 4hin issue comments. - Log actual time spent using
/spend 2h 30mfor development audits.
- Log estimated time using
Tab 3: Pull Requests (⇅ Pull Requests)
The enterprise code review, automated verification, and merge governance engine.
Key Capabilities & How to Use:
- Pull Request Template (.gitea/PULL_REQUEST_TEMPLATE.md):
Every PR automatically pre-populates with standard review sections:
- Description and motivation.
- Issue linking (e.g.,
Closes #14orFixes #28). - Change classification checkbox matrix.
- Verification and testing evidence (screenshots, terminal test outputs).
- Pre-merge compliance checklist (linting, tests, checksum updates).
- Automated Quality Gate Integration:
- Pull requests trigger .gitea/workflows/pr-quality-gate.yaml.
- Enforces minimum Go test coverage (>60%), zero TypeScript compiler errors, and cryptographic signature verification against
checksums.sha256.
- Mandatory Code Owner Review:
- Changes to files governed by
.gitea/CODEOWNERSautomatically request reviews from designated technical teams. - Branch protection blocks merging until designated code owners submit an approving review.
- Changes to files governed by
- Merge Strategies Enforced:
- Squash and Merge: Combines feature branch commits into a single atomic commit with Conventional Commit messaging.
- Rebase and Merge: Fast-forwards commits cleanly onto
mainwithout merge bubbles. - Create Merge Commit: Standard two-parent merge commit for large subsystem integrations.
- Automatic Issue Closure:
- When a PR is merged, keywords in the description (
closes #X,fixes #X,resolves #X) automatically close the linked issues and update project Kanban boards.
- When a PR is merged, keywords in the description (
Tab 4: Actions (Actions)
The continuous integration, continuous delivery, and operational automation engine.
Key Capabilities & How to Use:
- Thirteen Enterprise Workflows:
- Full reference documentation is available in the [[Gitea-Actions-Workflows]] handbook.
- Workflows include static analysis (
ci.yml), quality gates (pr-quality-gate.yaml), Coolify automated deployment (deploy.yaml), multi-architecture container publishing (docker-publish.yml), public documentation deployment (docs-site.yaml), Playwright browser tests (e2e-qa.yaml), PostgreSQL migration QA (migration-test.yaml), ThreadSanitizer race detector (race-detector.yaml), security audits (security-qa.yaml), and emergency rollbacks (rollback.yaml).
- Live Build & Runtime Log Streaming:
- Workflows stream deployment and build logs directly to the browser console line-by-line via REST API integration.
- Secrets Management:
- Configure encrypted secrets in Repository Settings -> Actions -> Secrets:
GITEA_TOKEN: Package and release automation token (073eb9a9bbdf4f7d33b50d4c7d0b53efd023392b).COOLIFY_URL:https://server.projectdefcorp.comCOOLIFY_DEPLOY_TOKEN/COOLIFY_TOKEN: Coolify management API token.COOLIFY_APP_UUID:bmqut3ytvlfk2yvsju2ywbr9COOLIFY_PROJECT_UUID:2omxwnodfypkn2nljida2g1mCOOLIFY_ENVIRONMENT_UUID:vcv3hwepjdjixasxkfq6twb0COOLIFY_DOCS_APP_UUID: Target public documentation identifier.COOLIFY_FQDN:https://origin.projectdefcorp.com
- Configure encrypted secrets in Repository Settings -> Actions -> Secrets:
- Manual Dispatch Execution:
- Select any workflow with
workflow_dispatch-> click Run workflow -> supply required inputs (e.g., target ref or log line count) -> monitor progress in real time.
- Select any workflow with
Tab 5: Packages (Packages)
The integrated, sovereign OCI and Docker Container Registry.
Key Capabilities & How to Use:
- Container Image Distribution:
- Hosts the official Origin by Corvus multi-architecture container images:
- Image URL:
git.projectdefcorp.com/quantum-tiger/origin-corvus:v1.0.0 - Supported architectures:
linux/amd64andlinux/arm64.
- Image URL:
- Hosts the official Origin by Corvus multi-architecture container images:
- Registry Authentication:
- Authenticate Docker CLI or container runtimes via token:
echo "073eb9a9bbdf4f7d33b50d4c7d0b53efd023392b" | docker login git.projectdefcorp.com --username oauth2 --password-stdin
- Authenticate Docker CLI or container runtimes via token:
- Pulling Images Directly:
docker pull git.projectdefcorp.com/quantum-tiger/origin-corvus:v1.0.0
- Client Access Scopes:
- Pre-authorized token
073eb9a9bbdf4f7d33b50d4c7d0b53efd023392bprovides read access to both packages and repository files (read:packages,read:repository).
- Pre-authorized token
Tab 6: Projects (Projects)
Kanban-style project tracking and agile sprint board management.
Key Capabilities & How to Use:
- Board Architecture:
- Project boards provide cross-functional visibility across engineering, QA, devops, and security.
- Standard columns:
- Triage / Incoming: Newly filed defects and capability proposals.
- Sprint Backlog: Prioritized items scheduled for the current sprint.
- In Progress: Actively being worked on by engineers.
- In Review: Pull request submitted, awaiting code review and quality gates.
- Done / Verified: Merged to trunk and validated in staging.
- Card Automation:
- Issues and pull requests automatically advance across columns when their status labels or PR review states change.
- Milestone Alignment:
- Boards map directly to active enterprise milestones (
v1.0.0 General Availability,v1.1.0 Enterprise Hardening).
- Boards map directly to active enterprise milestones (
Tab 7: Releases (Releases)
The official release distribution portal for versioned binaries, container digests, and changelogs.
Key Capabilities & How to Use:
- Release Numbering & Semantic Versioning:
- Follows strict SemVer:
vMAJOR.MINOR.PATCH(e.g.,v1.0.0,v1.1.0).
- Follows strict SemVer:
- Automated Changelog Generation:
- .gitea/scripts/generate_changelog.py automatically parses commit history and categorizes changes into features, bug fixes, performance improvements, and security patches.
- Cryptographic Release Attachments:
- Official releases bundle:
install.sh: Production Linux/macOS deployment script.install.ps1: Production Windows deployment script.checksums.sha256: Authoritative cryptographic SHA-256 digests.- Source code tarballs (
.tar.gz,.zip).
- Official releases bundle:
- Verifying Release Signatures:
- System administrators verify release integrity prior to installation using:
sha256sum -c checksums.sha256
- System administrators verify release integrity prior to installation using:
Tab 8: Wiki (Wiki)
The internal engineering knowledge base, architecture repository, and operational runbook portal.
Key Capabilities & How to Use:
- Git-Backed Knowledge Base:
- The entire wiki is an independent Git repository. Engineers can clone, edit locally, and push changes:
git clone https://git.projectdefcorp.com/Quantum-Tiger/Origin-By-Corvus.wiki.git
- The entire wiki is an independent Git repository. Engineers can clone, edit locally, and push changes:
- Structure & Navigation:
- Multi-page navigation is driven by
_sidebar.mdand_footer.md. - Internal wiki links use double bracket notation:
[[Page-Name]]or[[Target-Page|Custom Display Text]].
- Multi-page navigation is driven by
- Strict Confidentiality Boundary:
- Internal Developer Wiki (Gitea): Reserved for compilation runbooks, Go backend profiling, Coolify internal APIs, and security hardening procedures.
- Public Client Documentation: Hosted on Docusaurus at
docs.origin.projectdefcorp.com(https://origindocs.projectdefcorp.com/wiki). Internal engineering notes are never published to public client portals.
- Core Wiki Pages Directory:
Developer-and-Build-Handbook: Compiling Go server, bundling React webapp, live reload.Gitea-Actions-Workflows: Complete 14-workflow CI/CD handbook.Coolify-Deployment: Coolify API deployment, environment variable configuration, and log streaming.Security-Hardening: Defense-in-depth model, cryptographic salts, TLS 1.3, CSP headers.Backup-and-Disaster-Recovery: PostgreSQL snapshots, MinIO S3 replication, restoration runbooks.Quick-Start: Client single-line automated installers.Installation-Guide: Comprehensive bare-metal and container stack setup.Platform-Requirements-and-Sizing: Sizing specifications from 50 to 20,000 users.
- Automated Synchronization from
docs/:- The authoritative single source of truth for all technical documentation resides within
docs/in the core code repository. - Whenever guides in
docs/are modified onmain, the automated Gitea Actions workflow.gitea/workflows/wiki-sync.yamlautomatically transforms and synchronizes changes directly intoOrigin-By-Corvus.wiki.git. - Engineers edit once in
docs/, and both the Gitea Wiki and the Docusaurus portal remain 100% updated automatically.
- The authoritative single source of truth for all technical documentation resides within
Tab 9: Activity (Activity)
The real-time repository pulse, code churn audit, and team velocity dashboard.
Key Capabilities & How to Use:
- Pulse Overview:
- Displays real-time summaries of development activity: open vs. merged pull requests, closed vs. created issues, and active discussions.
- Commit Velocity & Code Churn:
- Visualizes commit volume over 7-day, 1-month, and 3-month windows.
- Audits lines of code added versus deleted across releases.
- Contributor Attribution:
- Highlights top contributors, active commit authors, and review turnaround times for engineering leadership audits.
- Operational Audit Trail:
- Serves as an unalterable operational log of repository actions, branch creations, tag pushes, and release events.
3. Administrative Settings & Configuration
Repository administrators manage core settings via the Settings menu (/settings):
- Repository Services (Units):
- Ensure all 9 tabs are enabled under Settings -> Repository -> Units (Repository Services):
- Code
- Issues
- Pull Requests
- Actions
- Packages
- Projects
- Releases
- Wiki
- Ensure all 9 tabs are enabled under Settings -> Repository -> Units (Repository Services):
- Branch Protection Rules (
/settings/branches):- Review and enforce protection rules on
main,production, anddevelopment.
- Review and enforce protection rules on
- Collaboration & Teams (
/settings/collaboration):- Manage team access permissions across
@Quantum-Tigerengineering groups.
- Manage team access permissions across
- Webhooks (
/settings/hooks):- Configure outbound webhooks to trigger external systems (Coolify, Slack/Origin notifications, monitoring systems).
4. Cross-Reference Index
- CI/CD Workflows Reference: [[Gitea-Actions-Workflows]]
- Issue Taxonomy & SLAs: .gitea/TAXONOMY.md
- Branch Protection Policy: .gitea/BRANCH_PROTECTION.md
- Code Ownership Rules: .gitea/CODEOWNERS
- Coolify Deployment Guide: [[Coolify-Deployment]]
- Production Installation Runbook: [[Installation-Guide]]