[codex] adopt shared Bazel package workflow#11
Conversation
Greptile SummaryThis PR replaces the fork's bespoke CI/CD config with the shared Confidence Score: 5/5Safe to merge — both workflows correctly enforce dry_run and no logic issues were found. Changes are limited to two GitHub Actions workflow files. The security-sensitive properties (commit-pinned reusable workflow reference, dry_run: true in both files, advisory-only lint/typecheck) are all correctly configured. No P0 or P1 findings were identified. No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A([push or pull_request to main]) --> CI
B([workflow_dispatch]) --> CI
B --> PUB
subgraph CI [ci.yml - CI]
CI1[js-bazel-package.yml at dde8c378]
end
subgraph PUB [publish.yml - Downstream Publish Rehearsal]
PUB1[js-bazel-package.yml at dde8c378 with github_package_name jesssullivan]
end
CI1 --> P1
PUB1 --> P1
P1[prepare: pnpm exec svelte-kit sync] --> P2
P2[advisory lint - continue_on_error true] --> P3
P3[advisory typecheck - continue_on_error true] --> P4
P4[unit tests and integration tests] --> P5
P5[build and package check] --> P6
P6[Bazel target pkg] --> P7
P7[dry_run true - publish rehearsal only]
Reviews (7): Last reviewed commit: "chore: adopt shared bazel package workfl..." | Re-trigger Greptile |
c2d688a to
663b931
Compare
Summary
dry_run: trueci-templatescommitWhy
The downstream fork should share the same rehearsal contract as the authoritative repos without pretending it is clean or publish-authoritative. This keeps the fork aligned while still reflecting its real state.
Validation
.github/workflows/ci.yml.github/workflows/publish.ymllintandcheckdebt