Skip to content

Labels

Labels

  • b4b

    bit-for-bit
  • blocked: answer changing

    Can't be resolved until we're ready for answer changes on master (non b4b)
  • blocked: dependency

    Wait to work on this until dependency is resolved
  • blocker

    another issue/PR depends on this one
  • branch tag: release

    Changes go on release branch as well as master
  • bug

    something is working incorrectly
  • closed: duplicate

    Issue already reported, or changes included in a different PR
  • closed: non-issue

    Not really a problem
  • closed: wontfix

    We won't fix this issue, because it would be too difficult and/or isn't important enough to fix
  • code health

    improving internal code structure to make easier to maintain (sustainability)
  • devops

    Development Operations to improve development throughput, E.g., adding GitHub Workflows
  • diagnostic

    Does not affect model outcome
  • docs-loc:?

    Location of needed change(s) is unknown
  • docs-loc:codebase

    Relates to documentation within the CTSM code. E.g., Readmes, code comments or tool help text.
  • docs-loc:infrastructure

    Relates to documentation infrastructure
  • docs-loc:lilac

    Relates to LILAC documentation
  • docs-loc:other

    Relates to documentation somewhere not covered by the other docs-loc labels.
  • docs-loc:tech-note

    Relates to Technical Note (science)
  • docs-loc:users-guide

    Relates to User's Guide (using CTSM/tools)
  • docs:?

    Type of documentation issue unknown
  • docs:infrastructure

    New features or bug fixes in the documentation infrastructure
  • docs:minor-content-fix

    Small fix needed to (or improvement suggested in) documentation content
  • docs:minor-tech-fix

    Minor technical fix needed to documentation content (e.g. broken link, broken rendering)
  • docs:new

    New documentation needed (e.g., for a new feature)
  • docs:update

    Significant update or fix needed to existing documentation
  • documentation

    additions or edits to user-facing documentation or its infrastructure
  • done

    Issues whose closing PR is done but not yet merged (pending test re-run ok)
  • enhancement

    new capability or improved behavior of existing capability
  • external

    issue needs to be addressed elsewhere (submodule); issue here for the sake of project tracking
  • FATES

    A change needed for FATES that doesn't require a FATES API update.