.forgejo — XeplosionGames

Conventions, standards, and infrastructure documentation for XeplosionGames.

This is the docs branch — the default branch of this repository and the first thing anyone sees when they open it. It contains no operational files. All sync workflows, shared templates, and scripts live on the main branch.

Note: Forgejo does not support org-level template inheritance — files in this repo do not automatically apply to other repos. They are distributed via the branch sync system on main.

---

Table of Contents

• Branches
• Documentation
• Quick Reference
  • Commit Convention
  • Branch Strategy
  • Labels at a glance

---

Branches

Branch	Purpose
docs	Default. This branch. Conventions and infrastructure documentation.
main	Operational. Sync system, shared workflows, issue templates, scripts.
template-issues	Template branch for issue-only repos
template-script	Template branch for script / infrastructure repos
template-dotnet	Template branch for .NET / MonoGame repos
template-node	Template branch for Node / web frontend repos
template-python	Template branch for Python repos
template-php	Template branch for PHP repos

---

Documentation

File	Contents
CONVENTION.md	Cross-stack conventions: Git, commits, PRs, project board
ISSUES.md	Issue types, triage workflow, lifecycle
LABELS.md	Label reference — all groups, names, and when to use them
PULL_REQUESTS.md	PR conventions, checklist, merge strategy
INFRASTRUCTURE-VPS.md	VPS server layout, users, permissions, CI/CD security
INFRASTRUCTURE-HUB.md	Hub server layout, users, permissions, CI/CD security

---

Quick Reference

Commit Convention

<type>: <description>.

Trailing period required. Common types: feat: fix: chore: docs: ci: perf: test: style:

Breaking changes: feat!: or fix!: or BREAKING CHANGE: in body.

Branch Strategy

Simple repos (infrastructure, config, single-service):

main  ← PRs merge here, deploys to production on push

Full repos (games, APIs, web apps):

dev   ← active development, deploys to test on push
main  ← stable, deploys to production on push

Feature branches: feature/description — Hotfixes: hotfix/description

Labels at a glance

Group	Rule	Common values
Kind/	Required, exclusive	Bug · Feature · Chore · Documentation · Security
Priority/	Encouraged, exclusive	Critical · High · Medium · Low
Resolution/	Required before leaving Triage, exclusive	Confirmed · Duplicate · Invalid · Won't Fix
Status/	Exclusive, manual	Needs Triage · Needs More Info · Blocked · Abandoned
Compat/	Stackable, PRs only	Breaking · Deprecation
Meta/	Stackable, anytime	Good First Issue · Help Wanted · Stale

See LABELS.md for full descriptions and usage guidance.