Labels

• category:bug

  The Issue/PR describes or solves a perceived malfunction within the game.
• category:feature

  The Issue/PR describes or implements a new game feature.
• category:refactoring

  The Issue/PR describes or contains an improved implementation.
• category:tweak

  The PR contains insignificant code changes, like code style grooming or value tweaking.
• component:AI

  The Issue/PR deals with the Python AI decision making code or affects it.
• component:art music text assets

  The Issue/PR deals with creating, modifying or verifying game assets.
• component:build system

  The Issue/PR deals with CMake, Visual Studio or the general build process.
• component:content scripting

  The Issue/PR deals with the FOCS language, turn events or the universe generator.
• component:deployment

  The Issue/PR deals with the deployment process or distribution packages.
• component:game mechanic

  The Issue/PR deals with the currently used or planned game mechanics.
• component:infrastructure

  The Issue/PR deals with development aiding infrastructure like CI, distribution or helper tools.
• component:internal

  The Issue/PR deals with any project component that has no explicit `component` label.
• component:network
• component:technical docs

  The Issue/PR deals with technical documentation like API, style, workflow or similar documentation.
• component:translation

  The Issue/PR provides or updates translations or deals with the translation process in general.
• component:UI

  The Issue/PR deals with the game user interface, graphical or other.
• component:user manual

  The Issue/PR deals with end-user documentation targeted towards players and server hosters.
• priority:high

  The Issue/PR is very urgent or important and should be addressed/finished as soon as possible.
• priority:low

  The Issue/PR is of minor importance/urgency and can be set aside for more urgent tasks.
• status:abandoned

  The contributor providing the PR has stopped working on it.
• status:cherry-pick for release

  The PR should be applied to the currently open release branch.
• status:duplicate

  The topic of the Issue/PR is or was already covered by another Issue/PR.
• status:help wanted

  Other developers or external contributors are welcome to support developing this Issue/PR.
• status:invalid

  The Issue is not classified as a formal valid Issue report or applicable PR.
• status:merged

  All relevant commits of this PR were merged into the master development branch.
• status:resolved

  The Issue was resolved, either by answering properly or fixing the underlying bug.
• status:superseded

  The PR implementation is insufficient and a follow up implementation PR exists.
• status:testing requested

  The Implementation can't be tested sufficiently by the developer and require support.
• status:won't fix

  The Issue won't be fixed as implementation or maintainance effort required would be execessive.
• status:work in progress

  The PR contains some implementation but isn't ready for merging onto the main development branch.