SbloodyS commented on PR #17996: URL: https://github.com/apache/dolphinscheduler/pull/17996#issuecomment-3976103613
> Currently, when a new PR is merged into the dev branch, all other PRs — even those that have already passed CI — are required to update their branches and re-run CI before they can be merged. <img alt="image" width="1311" height="450" src="https://private-user-images.githubusercontent.com/200727089/556232714-79c57574-df26-46e6-b999-e0fe695cde08.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzIyNDQyNzIsIm5iZiI6MTc3MjI0Mzk3MiwicGF0aCI6Ii8yMDA3MjcwODkvNTU2MjMyNzE0LTc5YzU3NTc0LWRmMjYtNDZlNi1iOTk5LWUwZmU2OTVjZGUwOC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMjI4JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDIyOFQwMTU5MzJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1jZDliOWI0NmQ2NmRkNzAwMmZmM2YxMDBlZjM5MjJlNmU1OTJhZTk1ZTA1M2JlZTk2MzU1MTgyNDQ1ODQ3ZWI0JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.0OcIwdvTcBxB hnAmdx4409XsZ_lypb0GPngn-KTp1EI"> > > This means that even PRs unrelated to the recent changes must trigger CI again, which can: > > * Increase unnecessary CI runs > * Consume additional CI resources > * Add extra operational overhead for contributors > > I’m wondering whether we could consider a workflow similar to SeaTunnel: > > * If there is a merge conflict with the latest dev, the contributor resolves the conflict and re-runs CI. > * If there is no conflict, re-running CI would not be required. > > This might help reduce redundant CI executions and improve overall efficiency. The consensus of PMC/Committer in this community determines that contributors do not need to pay attention to it for the time being. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
