🇺🇦 Sviatoslav Sydorenko (Святослав Сидоренко)

Yeah, I is similar to what I do with pre-commit tool: I exclude lots of files in config and then include them. I would probably like to see this as...

Well, it's the easiest way of keeping configs of all repos, where GitHub App is installed. Otherwise, you'd have to implement some per repo state management on the server side...

I'd say `.black_out.yaml` (toml?) in root or under some subfolder like `.github/` (with some precedence). But it also could be `pyproject.toml` section (which feels more relevant to Python projects).

Remark: blackening files wholesale creates unwanted side effects. I saw ppl resisting to it because it messes up authorship in `git blame`, for example. So I'd also suggest that this...

Further ideas: use a brand-new change suggestions feature to send chunk changes on top of PRs. https://blog.github.com/2018-10-16-future-of-software/#suggested-changes-public-beta

@Mariatta so this feature is nothing more than "```suggestion" type of the markdown code block. I bet it should work for the bot posting a comment to the position in...

@sloria pre-commit's hooks (I assume you're talking about pre-commit.com tool) don't always do changes, that's why I guess it's hard to use it for such a thing.

Err.. not exactly. It will run hooks and those hooks _may_ modify files if they are programmed to do so. Most of "hooks" there are linters, not autoformatters. Which conflicts...

Okay, I see where you're going with this. Makes sense.

@TheComet93 `emerge -s` shows that you have obs-studio installed, but there's no available. You have to sync db with either `eix-sync` or `emerge --sync`