Kitsios Konstantinos

Thanks both for your prompt and detailed feedback. Soon I will clear up some time and I can start an exploration of option 1 in a local fork to see...

Hi @LuKrO2011, @BergLucas, I have some time to work on this now. Based on our previous discussion, you had reached the conclusion that > option 1 is therefore the "easiest"...

Thanks, I'll give it a run with `--only-cover` and see how it goes. More probably than not, I will eventually need to go for line-level targets though. In that case,...

Thanks for your prompt reply. I think what you describe can be achieved by the following syntax (given that we insert it in all .yml files), but I will test...

> We want the CI "all green" on code which will be used. If we would cancel builds this might not be the case if a lot of stuff is...

> can you confirm the the groups are just enforced across repos/forks and not globally? Otherwise the group needs to add ${{ github.repository }} I confirm; workflows in this repo's...

> even though no merge conflicts are shown the changes from various PRs might not be compatible with each other Oh, I see, that makes sense! > We had the...

> It should be This will have the same effect with the changes in this PR, under the condition that from a single branch, only one PR can be opened.

> I cannot think right now - it is just too warm ... :D Thanks for the echo results. I will also have another look and try to prepare a...

In the meantime, you may also have a look at this one: https://github.com/danmar/cppcheck/pull/7641 The change is much simpler, we would be curious to see what you think of the idea.