Greg Dubicki

I resolved the conflicts and did a small refactor that I felt was necessary: after the cli arg rename from `-i` to `-e` the `iregex` name became inconsistent and misleading....

Thanks for the PR https://github.com/your-tools/tsrc/pull/366, @cgestes! Please see https://github.com/your-tools/tsrc/pull/376 where a docs change related to `pipx` vs `pip` is included.

Please try out [v3.4.0rc1](https://github.com/gitlabform/gitlabform/releases/tag/v3.4.0rc1) with this feature and a syntax working like described above, @weakcamel. Let me know what you think!

Big thanks for the tests @Siythrun and @weakcamel! I did also notice that transforming from the old syntax is not working like it should too - the groups seem to...

Have you tried using `applies_to_all_protected_branches: true`, @Siythrun ? The „all branches” is not supported by the GitLab API but it can be implemented, sure. But I prefer to root out...

Please check out [v3.4.0rc1](https://github.com/gitlabform/gitlabform/releases/tag/v3.4.0rc1) with this feature and a syntax working like described [here](https://github.com/gitlabform/gitlabform/issues/388#issuecomment-1278213194). Please note that for renaming of the rules to work you need to use `enforce: true`...

I am going to close this as I was not able to reproduce it. Please reopen if you still have the problem, @bethmal or anyone else.

Thanks @jpiron. I noticed this **again** in my GitLab instance and the new SSH key does not have spaces in the comment...

...but what you wrote about adding a comment with spaces enabled me to finally reproduce it with 100% reproducibility in a test, so thanks for that! :) Now I can...

The fix in [v3.3.1](https://github.com/gitlabform/gitlabform/releases/tag/v3.3.1) resolves the issue for me. Please try it out and let me know about your results!