EvanYao826andQuantumGhost 2c518c03f6 fix(ci): make no-new-getattr guard stable in shallow PR checkouts ...

The check_no_new_getattr guard could fail when CI checked out a shallow
synthetic PR merge commit, then fetched a newer main tip with --depth=1.
git merge-base failed because the PR base commit wasn't reachable from
the shallow-fetched main ref.

Fix:
- Use GITHUB_BASE_SHA (set by GitHub Actions for PR events) as the stable
  base commit reference instead of relying on git merge-base against a
  moving, shallow-fetched main branch.
- Remove the now-unnecessary git fetch/bind steps from style.yml.
- Add unit tests for the GITHUB_BASE_SHA fallback in resolve_ci_base.

Fixes #38325

2026-07-07 09:59:27 +08:00

..

ast_grep_rules

chore(api): disallow builtins getattr variants in new code (#38250)

2026-07-02 06:32:46 +00:00

stress-test

fix(api): scope nested resource lookups by owner refs (#38177)

2026-06-30 08:19:58 +00:00

check_no_new_getattr.py

fix(ci): make no-new-getattr guard stable in shallow PR checkouts

2026-07-07 09:59:27 +08:00