Skip to content

Labels

Labels

  • area:ci

    Build, test, release, labels, project automation, or repository plumbing.
  • area:community

    Discussions, wiki coordination, playtests, issue triage, or community ops.
  • area:crew

    Crew roles, traits, stress, energy frequency, hiring, or resting.
  • area:economy

    Markets, prices, goods, supply, demand, news effects, or couriers.
  • area:galaxy

    Galaxy generation, regions, systems, stations, factions, or station kinds.
  • area:lore

    Worldbuilding, civilisations, factions, storylines, or narrative canon.
  • area:mods

    Mod manifests, validation, data registry, examples, or compatibility.
  • area:save

    Save/load, migrations, storage, abandon campaign, or compatibility.
  • area:ship

    Ship modules, hardpoints, hull, cargo, drive, shield, sensor, or utility.
  • area:travel

    Routes, events, fuel, transit choices, hazards, or arrival flow.
  • area:ui

    Screens, layout, controls, mobile ergonomics, styling, or accessibility.
  • blocked

    Cannot proceed until a dependency, decision, permission, or upstream fix lands.
  • bug

    Something isn't working
  • channel:alpha

    Targets alpha promotion, playtest, pre-release, or alpha build work.
  • channel:development

    Targets the development branch and dev build channel.
  • channel:stable

    Targets main/stable release readiness or post-alpha release work.
  • dependencies

    Pull requests that update a dependency file
  • documentation

    Improvements or additions to documentation
  • duplicate

    Tracks work already covered by another issue or pull request.
  • enhancement

    New feature or request
  • good first issue

    Scoped, documented, and suitable for a new contributor.
  • help wanted

    A contributor can pick this up without blocking core roadmap work.
  • in-progress

    Work has started but is not yet ready for review.
  • invalid

    Not actionable as filed or does not apply to this repository.
  • javascript

    Pull requests that update javascript code
  • priority:p0

    Drop everything: release-blocking, data-loss, build-breaking, or critical play blocker.
  • priority:p1

    High priority: milestone blocker or serious player/contributor impact.
  • priority:p2

    Normal priority: planned roadmap work or important polish.
  • priority:p3

    Low priority: backlog, nice-to-have, cleanup, or future candidate.
  • question

    Needs clarification before implementation, triage, or prioritisation.