Thibault Jamet

Hi! If I may, I had a similar case that I happen to have open-sourced recently. In my case, I am pushing a given sha, but the logic would probably...

@dependabot rebase

Hi! Thanks for your contribution, those are a lot of changes at once. Would you mind splitting it into smaller PRs? Probably: 1 PR for golang update 1 PR for...

actually, as part of investigating #200 I envision applying the version updates independently. I would though encourage you to submit an updated PR with the rest of the changes.

Hi! Depending on how you installed the `kubectl` command, it can be related to this. Indeed, some distributions like rancher desktop does not install the actual `kubectl` but a wrapper...

Hi! Thanks for raising. In principle, maiao will do 2 things: 1. rebase your changes on top of the target branch. you can disable this by using the `--no-rebase` 2....

Would you have the ability to run it twice in a verbose mode (anonymising private fields)? indeed, this workflow, in standard conditions, is the one I use and I don't...

Hi! So far handling this is delegated to the user. The main reasoning of doing so is that there is high risk of rebase conflict and for the simplicity of...

@joaoqalves the change-id is indeed generated as a sha of the intended changes (see it as a partial commit sha). It is a git hash including remarkably the initial parent...

Thanks for your input. We didn't have the time to look at it yet, but will try to reproduce it locally to see how we can provide a solution for...