mirror of
https://github.com/garrytan/gstack.git
synced 2026-11-22 08:01:32 +01:00
Ship policy can mark published data as content, so /ship can review large data PRs (GST-3158) (#4511)
A repo can now list published-data folders under a new `review_content_patterns` ship-policy key, so /ship leaves `.patch` diffs, `MANIFEST.sha256` and extension-less licences out of review, while source files there stay reviewed. Why: gstack-evals #352 is 13.8 MB, 13.6 MB of it published session data, and could never pass /ship's 2 MB review limit. Nothing to do until a repo adds the key to its base-branch policy; a pattern that keeps too many files now stops with `REVIEW_EXCLUDE_KEEP_TOO_LARGE` instead of being dropped. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> Review-Finding: p1/red-team#2 reader=red-team Review-Finding: p2full/red-team#1 reader=red-team
This commit is contained in:
1 parent
c25390daa2
commit
f13dbb0d4a
11 files changed
+340
-48
No files matched your search
@@ -371,6 +371,7 @@ gstack_result_anchor() {
|
||||
PR_WAIT_REFUSED) printf '%s' 'pr-wait-refused' ;;
|
||||
PREGATE_HEAD_POLICY_LOOSENS) printf '%s' 'pregate-head-policy-loosens' ;;
|
||||
REVIEW_DIFF_TOO_LARGE) printf '%s' 'review-diff-too-large' ;;
|
||||
REVIEW_EXCLUDE_KEEP_TOO_LARGE) printf '%s' 'review-exclude-keep-too-large' ;;
|
||||
REVIEW_DIFF_UNREADABLE) printf '%s' 'review-diff-unreadable' ;;
|
||||
REVIEW_PLAN_STOPPED) printf '%s' 'review-plan-stopped' ;;
|
||||
REVIEW_EXCLUDE_REFERENCE) printf '%s' 'review-exclude-reference' ;;
|
||||
|
||||
Reference in new issue
Block a user