linguini1 commented on PR #17184: URL: https://github.com/apache/nuttx/pull/17184#issuecomment-3390777759
> Previously, multiple workflows could trigger independently on the same event (e.g., a new commit or PR update), causing redundant CI executions — even when earlier checks had not completed or when the PR was in a draft state. > > With this change, CI stages are serialized using the workflow_run mechanism. This allows one workflow to trigger another only after it successfully completes (e.g., running build/test workflows only after Check passes). I think not running workflows on draft PRs is good, but why don't we want a new commit to re-trigger the workflow? Otherwise we're wasting time finishing the first CI on stale commits and then the new CI will run right after, so it would be double the time? -- 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]
