.forgejo

Organization defaults and repository standards for Xeplosion Technologies, LLC.

This repository does two jobs. It holds the shared conventions every Xeplosion Technologies project follows, and it distributes the files that enforce them to every template and project repository.

If you are here to understand how we work, you only need the first table.

---

Standards

Start here. No tooling required.

Document	Covers
docs/WORKFLOW.md	Git workflow, branch strategy, commit conventions, development lifecycle
docs/ISSUES.md	Issue triage, project-board stages, review gates, completion requirements
docs/PULL_REQUESTS.md	Pull request workflow, issue linkage, review expectations, merge practices
docs/LABELS.md	Organization-wide issue and pull request label taxonomy

The standard issue workflow is:

Triage → Backlog → To Do → In Progress → [In Review] → Completed

In Review is used when the complexity or criticality of the work warrants explicit validation before completion.

Use enough structure to protect maintainability, traceability, and quality, but do not create ceremony for its own sake. When choosing between the quick path and the structured path, ask:

Will doing this the quicker way create technical debt or make the project harder to maintain later?

If not, keep it simple.

---

Templates

New repositories are created from a template repository. Each one is published from a template-* branch of this repository, and each keeps itself current afterwards by pulling shared files back from here.

Template	For
template-issues	Issue tracking only — no code
template-script	Shell utilities and operational scripts
template-node	Node / TypeScript services
template-python	Python services
template-php	PHP services
template-dotnet	.NET projects

If you maintain a repository created from one of these, you do not need to do anything: a pull request appears when shared files change.

docs/TEMPLATES.md explains how the distribution works and how to change what gets distributed.

---

Repository layout

Path	Contents
docs/	The standards above
ISSUE_TEMPLATE/, pull_request_template.md	Org-wide defaults — and the source synced to every template
shared/	Payload distributed to template branches. Nothing here runs in this repository
sync/manifest.yml	What is distributed, where, and under which rule
tools/xetool.py	Validates the manifest and performs the distribution
.forgejo/workflows/	This repository's own automation
labels.yml	Machine-readable label definitions behind docs/LABELS.md

The distinction that matters: shared/workflows/deploy-production.yml is a file this repository hands out and never executes. .forgejo/workflows/sync.yml is a workflow this repository actually runs.

---

Scope

These conventions apply across Xeplosion Technologies repositories unless a repository documents a justified exception. Repository-specific or stack-specific rules may extend them, but should not contradict them without a clear reason.

The Forgejo Wiki carries expanded guidance, examples, and operational walkthroughs where more explanation is useful.