Rebasing git repository is not sufficient as component updates also consider component version range for release notes. Rather fail current component update build and trigger resource check, so next iteration will succeed.
We could also consider to check whether there will be merge conflicts prior to opening PR so there will be less noise, however I am not sure as this seems more error prone to me.
Rebasing git repository is not sufficient as component updates also consider component version range for release notes. Rather fail current component update build and trigger resource check, so next iteration will succeed.
What this PR does / why we need it:
Which issue(s) this PR fixes: Fixes #
Special notes for your reviewer:
Release note: