DanielLeens opened a new pull request, #11540:
URL: https://github.com/apache/seatunnel/pull/11540

   ## Why
   The previous branch protection change made `Build` required and also set 
`required_status_checks.strict: true`.
   
   That enforces an extra gate beyond required CI: every PR branch must be 
updated to the latest `dev` and re-run checks before merge. In practice, an 
approved PR with a successful `Build` can still be blocked only because it is 
behind `dev`.
   
   PR #11525 is one concrete example: it had approval plus successful `Build`, 
but GitHub still blocked merge because the branch was behind `dev`.
   
   ## What changed
   - keep `Build` as the required status check
   - change `required_status_checks.strict` from `true` to `false`
   
   This preserves the intended gate of "CI must pass before merge" without 
forcing every PR to sync with the latest `dev` before merge.


-- 
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]

Reply via email to