Skip to content

Labels

Labels

  • special: load testing

    Tasks involving stress or load testing environments.
  • special: maintenance window

    Scheduled downtime or upgrades requiring coordination.
  • special: non-code

    Tasks that are unrelated to the codebase but support the project (e.g., marketing, outreach).
  • special: performance

    Tasks to improve app speed or efficiency.
  • special: provisioning

    Setting up infrastructure-as-code or similar provisioning tools (e.g., Terraform, Ansible).
  • special: scaling strategy

    Planning or executing strategies for horizontal or vertical scaling.
  • special: wontfix

    Issues that will not be addressed for specific reasons.
  • status: backlog

    Not yet started, waiting to be prioritized.
  • status: blocked

    Blocked by another issue or dependency.
  • status: completed

    Fully implemented and verified.
  • status: deprecated

    Indicates that a feature, codebase, or component is no longer actively supported.
  • status: in progress

    Currently being worked on.
  • status: needs feedback

    Waiting for input or feedback from stakeholders or contributors.
  • status: needs review

    Ready for code or design review.
  • status: pending approval

    Tasks requiring review or approval before execution (e.g., changes to critical infrastructure).
  • status: rollback completed

    Indicates a rollback has been executed and verified.
  • status: rollback needed

    Indicates that a rollback is planned or in progress for a failed deployment.
  • status: testing in progress

    Task is currently being tested.
  • testing: automation

    Tasks related to writing or maintaining automated tests.
  • testing: edge cases

    Specific scenarios or edge cases that need testing.
  • testing: manual required

    Tasks requiring manual testing.
  • type: analytics

    Tasks related to implementing or improving analytics and tracking.
  • type: backup & recovery

    Tasks to implement or improve backup and disaster recovery mechanisms.
  • type: brainstorming

    Open-ended discussions or tasks requiring input from multiple contributors.
  • type: bug

    Reports of broken or incorrect behavior.
  • type: CI/CD

    Tasks involving Continuous Integration/Continuous Deployment pipelines.
  • type: cleanup

    Tasks to clean up code, assets, or other components.
  • type: compliance

    Tasks to ensure systems meet regulatory or organizational compliance requirements (e.g.GDPR, SOC 2)
  • type: configuration

    Changes or updates to configuration files or settings.
  • type: configuration drift

    Tasks related to identifying and resolving inconsistencies between environments.