mirror of
https://github.com/Sea-Haven-Industries/.github.git
synced 2026-09-30 23:23:11 +00:00
Adam Moussa
d31893d318
The central label rules assumed a root-level project layout (lib/**, bin/**, cdk/**, src/**), so monorepos that nest components under top-level dirs (infra/, web/, mobile/, shared/) matched nothing for those areas. PRs touching only infra/lib/** or web/** ran the labeler green but received no label. Label coverage: - infra: + 'infra/**' (covers infra/lib, infra/bin, infra/cdk.json) - app: + 'web/**', 'mobile/**', 'shared/**' Additions are appended to the existing root paths, so single-project repos are unaffected; deliberately avoided blanket '**/lib/**' globs that would mislabel web/src/lib/** as infra. Hardening rolled in while here: - Pin actions/labeler to a commit SHA (was the floating @v6 tag) - Add a per-PR concurrency group with a run_id fallback for non-PR callers, so rapid pushes cancel superseded label runs - Broaden 'ci' (.github/actions/**), 'dependencies' (Directory.Packages.props, yarn.lock, pnpm-lock.yaml, Podfile/.lock) and 'tests' (JS/TS .test/.spec, pytest test_*.py/conftest, .NET *Tests.cs, Java *Test.java, Go, Ruby) globs Caller repos must already have any label a rule can emit; actions/labeler does not create missing labels. The org 'infra' label was backfilled across repos separately. |
||
|---|---|---|
| .. | ||
| callable-dependency-review.yaml | ||
| callable-labeler.yaml | ||
| cd-cdk.yaml | ||
| cd-mobile-ios.yaml | ||
| cd-sam.yaml | ||
| ci-dotnet.yaml | ||
| ci-python-app.yaml | ||
| ci-python-sam.yaml | ||
| ci-static.yaml | ||
| ci-typescript-cdk.yaml | ||
| ci.yaml | ||
| compliance-audit.yaml | ||
| labeler.yaml | ||