Skip to content

Labels

Labels

  • autorelease: pending

  • autorelease: tagged

  • good first issue

    Good for newcomers; small, well-scoped, low context needed.
  • help wanted

    Maintainer would welcome outside help on this.
  • ⚙️ settings

    Game setup, user-configurable options, preferences screens, or rules customization controls.
  • ⚡ p1

    High-priority work needed for the next meaningful milestone or core gameplay path.
  • ⛔ blocked

    Cannot proceed until a dependency, decision, asset, or prerequisite issue is resolved.
  • ✅ ready

    Well-scoped, unblocked, and ready for implementation or review work to begin.
  • ✨ polish

    Usability, visual quality, accessibility, performance, responsiveness, or player-feel improvement.
  • ❓ question

    Open product, rules, technical, or design question that needs a decision before implementation.
  • 🃏 cards

    Card model, deck copies, card faces/backs, melds, hands, or card rendering concerns.
  • 🃟 jokers

    Joker identity, placement choice, replacement, memory display, restrictions, or visuals.
  • 🌍 localization

    Localization architecture, English/Arabic strings, terminology, RTL readiness, or translations.
  • 🎨 design

    Visual design, interaction design, product tone, layout, animation, or design review work.
  • 🎮 playable loop

    Work required for a complete playable Classic Hareeg round/match loop.
  • 🏗️ foundation

    Foundation milestone work: architecture, CI, project setup, shell, and core scaffolding.
  • 🐛 bug

    A confirmed defect, regression, crash, incorrect behavior, or broken user flow.
  • 👀 needs review

    Implementation or design is ready for human/code review before merge or closure.
  • 💾 persistence

    Local storage for settings, preferences, match state, resume, or history.
  • 📌 prd

    Parent PRD with scope, stories, decisions, and child tracker.
  • 📏 rules

    Classic Hareeg rule-engine behavior, validation, turn state, scoring, or rule presets.
  • 📚 docs

    Repository docs, in-app help, rules documentation, contributor docs, or issue/PR templates.
  • 🔥 fifty

    Fifty/Khamsin claim flow, timer, validation, scoring, penalties, or visual treatment.
  • 🔮 future

    Explicitly out-of-scope or later-release work such as Hareeg 14, Fifties mode, or online play.
  • 🔹 p2

    Normal-priority work that matters but does not block the immediate critical path.
  • 🖥️ ui

    Flutter screens, navigation, table layout, controls, feedback states, or responsive UI.
  • 🙋 hitl

    Requires human-in-the-loop judgment for rules, naming, design, tone, or product behavior.
  • 🚦 ci

    GitHub Actions, analysis/test automation, build checks, release checks, or toolchain health.
  • 🚧 in progress

    Actively being worked on; avoid duplicate effort unless coordinating with the owner.
  • 🚨 p0

    Critical issue that blocks basic project viability, correctness, or release readiness.