Documentation
¶
Overview ¶
Command ax-pin-check compares examples/deploy/ax's pinned AX runner commits (.ax-ref on google/ax and .ax-fork-ref on mastersingh24/ax) against upstream and fork main branches, and renders the job summary and rolling-issue body used by .github/workflows/ax-pin-check.yml (#1410).
Four GitHub API calls per run (#1418):
- compare google/ax .ax-ref...main: upstream movement and the watched files that changed;
- compare mastersingh24/ax .ax-fork-ref...main: fork movement;
- compare mastersingh24/ax .ax-ref...main: the fork's patch stack on top of the upstream pin. This one 404s if the fork has not fetched the upstream commit named by .ax-ref, and the run errors rather than filing an issue. That is deliberate: a fork that does not contain the upstream pin is a pin problem, not a drift report;
- GET /repos/{repo}/commits/heads/{branch} for each head SHA. The compare payload's commits[] is capped at 250 and its files[] at 300; GitHub documents that on an unpaged call the last listed commit is still the tip, but that is a property of the pagination defaults, not of the endpoint. The branch tip is read from the endpoint whose job that is, and a failed lookup is an error rather than a silent fallback to the pin.
Click to show internal directories.
Click to hide internal directories.