Skip to content

Labels

Labels

  • A0-pleasereview

    Pull request needs code review.
  • A1-onice

    Pull request is reviewed well, but should not yet be merged.
  • A2-insubstantial

    Pull request requires no code review (e.g., a sub-repository hash update).
  • A3-inprogress

    Pull request is in progress. No review needed at this stage.
  • A3-stale

    Pull request did not receive any updates in a long time. No review needed at this stage. Close it.
  • A4-awaitingci

    Pull request is waiting for changes on the CI to complete tests before review/merge can begin.
  • A4-clasignoffneeded

    Pull request requires author to sign off on CLA before review/merge can begin.
  • A4-gotissues

    Pull request is reviewed and has significant issues which must be addressed.
  • A5-grumble

    Pull request has minor issues that must be addressed before merging.
  • A6-mustntgrumble

    Pull request has areas for improvement. The author need not address them before merging.
  • A6-revertrevert

    Pull request that reverts recent changes.
  • A7-looksgoodcantmerge

    Pull request is reviewed well, but cannot be merged due to conflicts.
  • A7-looksgoodtestsfail

    Pull request is reviewed well, but cannot be merged due to tests failing.
  • A8-backport

    Pull request is already reviewed well in another branch.
  • A8-looksgood

    Pull request is reviewed well.
  • A9-buythatmanabeer

    Pull request is reviewed well and worth buying the author a beer.
  • A9-FUCKYEAH!1

    Pull request is reviewed well and can not be compensated with any amount of beer in the galaxy ;)
  • B0-patchthis

    Pull request should also be back-ported to the beta/stable branch(es).
  • B1-releasenotes

    Changes should be mentioned in the release notes of the next minor version release.
  • dependencies

    Pull requests that update a dependency file
  • F1-panic

    The client panics and exits without proper error handling.
  • F1-security

    The client fails to follow expected, security-sensitive, behaviour.
  • F2-bug

    The client fails to follow expected behavior.
  • F3-annoyance

    The client behaves within expectations, however this “expected behaviour” itself is at issue.
  • F4-tests

    Tests need fixing, improving or augmenting.
  • F5-documentation

    Documentation needs fixing, improving or augmenting.
  • F6-refactor

    Code needs refactoring.
  • F7-footprint

    An enhancement to provide a smaller (system load, memory, network or disk) footprint.
  • F7-optimisation

    An enhancement to provide better overall performance in terms of time-to-completion for a task.
  • F8-enhancement

    An additional feature request.