Cristian Le

The failure is because it is run on a fork, these are resolved in #3108

I don't quite remember, but there were a bunch of broken links inside the rst generated file, but it so happened that linkcheck aggregated the report or something, don't quite...

> Hmm, blocked by #3108 :/ Or maybe superseded-by since that one contains the commit from here

For the `spellcheck` it seems @happz finds it usable in the current state, so I will deffer the implementation to them. I thought it didn't handle capitalization that well, e.g....

Another approach could be to separate only the `report` step? That way the `prepare` and `finish` steps can be shared. `execute` splitting might not be desired since it would lack...

It depends on what the goal for splitting the plans is. If it's for running the tests in parallel then this approach where all test steps are separated `prepare`, `execute`,...

You mean the `adjust` is done on the fmf files, not on the "merged" data that include `tmt run -a provision ...` steps?

Ok, but that' reassuring, the `adjust` is done after `tmt` injects `context` (probably that's how `distro` works and [sometimes not](https://github.com/teemtee/tmt/issues/2905)?), so we could provide a `provision_how` or equivalent context to...

Well at least the tests are happy so far, although there are no tests written for this. Can I leave writing these tests to the others? I'll just push a...

@lukaszachy I will need some help on [this](https://artifacts.dev.testing-farm.io/a005ffca-4f45-464f-b1ea-30bd1f20b3af/). Locally when I test I get appropriate failures, but tmt seems to detect a fmf root from somewhere. And it is not...