lulianqi opened a new pull request, #31:
URL: https://github.com/apache/dubbo-net/pull/31

   ## Summary
   
   Fixes #4.
   
   The build/unit-test and license-header workflows are already implemented. 
This PR proposes the remaining merge-gating configuration, also requiring the 
existing end-to-end check.
   
   - Add a separate **Required CI Checks** ruleset scoped only to the default 
branch.
   - Require the exact existing check contexts, with `github-actions` as the 
expected source:
     - `build-and-test`
     - `license-header-check`
     - `ZooKeeper, Nacos and direct protocols`
   - Preserve the existing Default Branch Protection ruleset, classic 
protection, and infrastructure `root` bypass. The new ruleset does not take 
over deletion or force-push restrictions.
   - Leave release branches outside the new check requirement: the current 
workflows target PRs to `main`, so requiring those contexts on release branches 
could leave their PRs waiting for checks that never run.
   - Do not change workflow triggers, client code, or the branch-up-to-date 
policy.
   
   This uses the ASF-supported [ruleset 
configuration](https://github.com/apache/infrastructure-asfyaml#rulesets). No 
live repository settings have been changed directly; the proposal remains 
subject to maintainer review and ASF synchronization after merge.
   
   ## Validation
   
   - YAML parsing passed.
   - A structural comparison confirms that every pre-existing configuration 
value is unchanged.
   - Required check names and source app slugs match actual checks on upstream 
`main`.
   - All three workflows trigger for PRs targeting `main`, with no PR path 
filters.
   - `git diff --check` passed.
   - Only `.asf.yaml` is modified; no runtime changes or workflow changes are 
included.
   
   After merge, please confirm that ASF has synchronized the ruleset and that 
GitHub reports these checks as required. Thank you for reviewing this 
repository-policy change.
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to