contrueCT opened a new pull request, #3297:
URL: https://github.com/apache/hugegraph/pull/3297

   ## Purpose of the PR
   
   Fixes #3296. A queued PR run currently accepts its old merge after 
same-repository retargeting or a target force-push to unrelated history. Plans 
and final gates now reject these stale targets while allowing normal 
target-branch advancement.
   
   ## Main Changes
   
   - Record and verify the target branch name in plans and result reports.
   - Check the tested base against the live target with the repository compare 
API; commits added after checkout need not be present locally.
   - Keep conservative selection and the existing Memory metadata-outage policy.
   
   ## Verifying these changes
   
   - [ ] Trivial rework / code cleanup without any test coverage. (No Need)
   - [x] Covered by regression tests: 56 Python tests pass, including real Git 
fixtures for retargeting, unrelated force-push, ordinary advancement and all 
three final gates.
   - [x] Java 17 whole-repository clean compilation, editorconfig formatting 
and `git diff --check` pass. A live repository comparison confirms the API 
status/merge-base fields used by the guard.
   
   ## Does this PR potentially affect the following parts?
   
   - [ ] Dependencies
   - [ ] Modify configurations
   - [ ] The public API
   - [x] Other affects: CI plan freshness and result reporting
   - [ ] Nope
   
   ## Documentation Status
   
   - [ ] `Doc - TODO`
   - [x] `Doc - Done`: `docs/ci.md` documents target-ref binding, ancestry and 
outage handling.
   - [ ] `Doc - No Need`
   


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