Olivier Vernin

That's a lot of information to process, so I'll try answer them one by one ## Version Increment Writing a policy that would do what you ask has been puzzling...

> Side-tracking: Specifying 2 different PRs from 2 different targets looked really cumbersome in my previous message @olblak: do you think we could have a way to link actions and...

Thanks for opening, what you reported is definitely an area where we need to improve. While I prefer reusing the same branch and how we use Updatecli, it has drawback...

Regarding merge conflicts, I noticed two different situations ** Old delete branches being reused** Updatecli sometimes reusing old deleted branches, I explained this issue on Github [here](https://github.com/orgs/community/discussions/16351#discussioncomment-6987143), I don't really...

This is still ongoing, I am experimenting with a new project named [udash](https://github.com/updatecli/udash) I currently have a demo environment deployed on https://app.updatecli.io 

Thank you both for your feedback. Let me explain how I ended up here. While adding Flux support, I realize that I couldn't handle Git repository as it has a...

I am closing as more I think about this issue and less I think it's the right way to solve my problem

Thanks for opening this issue, indeed you are right to highlight a scenario I forgot about. > The pipeline is skipped as the image does not exists meaning the condition...

The problem that I tried to fix in 0.65.0 has nothing to do with the dockerimage code but how we understand a pipeline result as a whole. Let's take the...

You are right, I'll release 0.65.1 within the day