Repo layout and conventions #1
Labels
No labels
area/ads
area/backend
area/ci
area/game
area/shell
game/barrel-climb
game/block-drop
game/centipede-garden
game/frog-crossing
game/hex-breaker
game/hive-invaders
game/maze-muncher
game/missile-shield
game/orbit-defender
game/snake-arena
good-first-issue
priority/high
priority/low
priority/medium
status/blocked
type/art
type/bug
type/chore
type/docs
type/feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
NetDagger/arcade#1
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Set up the top-level structure every game and service plugs into, and document it in
docs/CONVENTIONS.md.Acceptance criteria
docs/CONVENTIONS.mdcovers layout, naming (kebab-case slugs), labels, branching (main + feature branches) and commit styledocs/ROADMAP.mdlists milestones and game status.forgejo/ISSUE_TEMPLATE/