Labels

• area | automation

  Tools, actions and workflows automating our work
• area | check

  Test check implementation
• area | config

  User configuration
• area | context

  The context adjust implementation
• area | contribute

  Improving experience for tmt contributors
• area | dist-git

  Implementation related to integration with the dist-git repositories.
• area | environment

  Environment variables handling
• area | hardware

  Implementation of hardware requirements
• area | helper scripts

  Implementation of tmt-abort, tmt-file-submit, tmt-reboot, tmt-reboot-core and tmt-report-result.
• area | image mode
• area | libraries

  Issues related to beakerlib libraries support
• area | maintenance

  Changes important for efficiency and the long-term health of the project
• area | multihost

  Issues related to the multihost testing support
• area | package managers

  Changes related to implementations of package managers
• area | plan import

  Support for importing remote plans
• area | policy

  Implementation of the tmt policies used for globally modifying metadata.
• area | process

  The way how we collaborate on the development
• area | recipe

  Related to the tmt recipe handling
• area | restraint

  Backward compatibility support for restraint
• area | results

  Related to how tmt stores and shares results
• breakage

  Change will change current behaviour
• bug

  Something isn't working
• ci | full test

  Pull request is ready for the full test execution
• ci | skip

  Do not run any tests (useful for very early drafts).
• code | base

  Base classes implementation in base.py
• code | cleanup
• code | cli

  Changes related to the command line interface
• code | core

  Implementation of the core metadata level
• code | logging

  Changes related to debug logging
• code | no functional change

  "No Functional Change" intended. Patch should not change tmt's behavior in any way.