Alexander Schmolck

@Ericson2314 this actually required a bit of work to bring up-to-date and I also I also found a [small bug in nix-info](https://github.com/NixOS/nixpkgs/pull/229113) along the way and had to create a...

For what it's worth, I'm not sure if there's some reason to prefer converting to a hex float literal and then parsing that to just doing something something like `return...

Yes, my thinking was something like a `side-by-side-min-columns = 120` option in gitconfig rather than an env var, I think env var makes most sense for passing through flags directly...

@navarroaxel maybe overkill, but one option to future-proof (and self-document) it more would just be to make it more descriptive, e.g: ``` side-by-side = true | false | columns >...

@dandavison If you dislike introducing new flags, think just extending the meaning of the gitconfig option and keeping the commandline option a simple boolean switch is probably fine, especially since...

As @jcpetruzza noted, this would probably require a non-trivial amount of work since some (important) features still require SSH keys and we need to also test that the combination of...

I'm not sure what the relationship between CI running and rebase problems would be, can you please elaborate? Are you sure there wasn't just a rebase conflict?

Could you try running marge with debug output, and paste what actual Gitlab API call returns back (and also what version of gitlab you are using)? Not fully sure if...

I haven't used manual actions, but what you want (expensive CI actions only triggering when marge is attempting to merge) is very reasonable, and I think something we should support....

Yes, I'd like to do that, but it's not particularly high priority.