The latest-state copy of a record is slimmed too (#1129) #2674
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| name: OSS readiness | |
| # Repository-level open-source readiness gate. This job is intentionally | |
| # dependency-free (no Rust toolchain, no private git dependencies, no secrets) | |
| # so it stays green on any runner and enforces the hygiene contract described | |
| # in docs/open_source_readiness.md on every push and pull request. | |
| on: | |
| push: | |
| branches: | |
| - main | |
| - rust-main | |
| - oss-prod-readiness | |
| pull_request: | |
| # No `branches:` filter here, deliberately. This key filters on the BASE branch, and a | |
| # stacked pull request is based on the branch below it, not on main -- so this job did not | |
| # run on one at all. Worse, when the branch below it merged, GitHub retargeted the pull | |
| # request to main and did NOT re-run anything: the stale checks from the feature-branch | |
| # days stayed green and the pull request merged reporting success from a job that had | |
| # never seen it. Running on every pull request costs a few Actions minutes and is the only | |
| # way the gate covers the changes that actually reach main. | |
| workflow_dispatch: | |
| permissions: | |
| contents: read | |
| jobs: | |
| oss-readiness: | |
| runs-on: ubuntu-latest | |
| steps: | |
| - name: Checkout | |
| uses: actions/checkout@v4 | |
| with: | |
| fetch-depth: 0 | |
| - name: Set up Python | |
| uses: actions/setup-python@v5 | |
| with: | |
| python-version: "3.11" | |
| - name: Byte-compile maintainer tooling | |
| run: python -m py_compile tools/*.py | |
| - name: Validate open-source readiness contract | |
| run: python tools/validate_open_source_readiness.py |