@MakiWolf thanks for your PR. Can you please:

• Use multi-line-style C# comments (with /* instead of //) when commenting more than one line. This way you don't introduce git-blame noise, in case any of the lines need to be re-enabled later.
• Enable GitHubActions on your fork, so that we can see the CI status of your changes (after enabling GitHubActions, you need to repush this branch again).

@knocte Thank you for feedback.

• Use multi-line-style C# comments (with /* instead of //) when commenting more than one line. This way you don't introduce git-blame noise, in case any of the lines need to be re-enabled later.

I will do this in future.

• Enable GitHubActions on your fork, so that we can see the CI status of your changes (after enabling GitHubActions, you need to repush this branch again).

I have turned on github actions and here is the output: https://github.com/MakiWolf/dotdevelop/actions/runs/5647216462

I will do this in future.

You can still change it in this PR and if whoever merges it squashes commits, then the git-blame-noise is averted.

You can still change it in this PR and if whoever merges it squashes commits, then the git-blame-noise is averted.

@knocte I have made a commit now and changed this. But please note that this PR is experimental.