Benjamin Poldrack

Seems to me this is a problem solved. Feel free to reopen if that is a misjudgment.

Fixed the interactivity issue (it was the introduced test, not an actual code change), rebased and removed the disabling of parallel test execution again. Only remaining "failures" before that rebase...

Remaining failures are in macOS setup - see https://github.com/datalad/datalad/pull/7227 Actual code changes approved long ago - will go ahead and merge.

Skipping changelog commits rejected (see https://github.com/datalad/datalad/pull/7208). Otherwise I think we've settled on a procedure for now. Let's see how the 0.18 series goes.

> with such extensive change touching functionality I also wonder if may be worth/safer for master? Main reason for `maint` to me is, that we (as in Jülich) need this...

I think, this is ready, @yarikoptic. There's the `git-annex died of signal 11` on macos github action, but this seems unrelated.

@yarikoptic > I feel that there should be some "deeper" fix for interactivity detection I spend hours on this and couldn't find one. That's why this solution. > or annex-no-dialog...

@yarikoptic > yes -- if outside process datalad.ui.interactive set to "auto" , and it determines that it is interactive (or not), setting its env var DATALAD_UI_INTERACTIVE so any nested process...

> When I declare annex dead here in a repository that is in private mode (which it would be in this case, as private needs to be declared very early...

@yarikoptic > Note: this config is asked from the general datalad.cfg, i.e. not per dataset config. Yes, I added this aspect to the changelog. `Dataset.repo` evaluation from within the runner...