Repository navigation
Commit a7dea3d
authored
The PR-side marker-guard already runs in non-strict mode for
`upstream/merge-*` head_refs, but after a squash-merge of that PR,
the push event to main has no head_ref / second-parent / branch-name
signal — it falls back to `--strict` and fails on the hundreds of
upstream files the bridge merge brings in (98 false-positive warnings
on the v1.4.0 bridge merge, run 25264283463).
Detect bridge / upstream-merge commits in the pushed range by subject
(`grep -qiE '(bridge|merge) upstream'`) and downgrade strict->non-strict
for those pushes. Warnings still surface in job output; the PR-side
review already gated marker integrity for the change.
Validated locally:
- regex matches commit 3cc3d4c (v1.4.0 bridge merge)
- analyze.ts --markers --base <prev-main> exits 0 (97 warnings shown)
- --branding and --require-markers --strict both pass on main HEAD
- marker-parser tests: 22/22 passing
- ci.yml is valid YAML
Closes #781
1 parent 3cc3d4c commit a7dea3d
1 file changed
Lines changed: 12 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
441 | 441 | | |
442 | 442 | | |
443 | 443 | | |
444 | | - | |
445 | | - | |
| 444 | + | |
| 445 | + | |
| 446 | + | |
| 447 | + | |
| 448 | + | |
| 449 | + | |
| 450 | + | |
| 451 | + | |
| 452 | + | |
| 453 | + | |
| 454 | + | |
| 455 | + | |
446 | 456 | | |
447 | 457 | | |
448 | 458 | | |
| |||
0 commit comments