Apply Timeline
Find the exact repository event, semantic diff, checks, and apply phases behind a business change.
Find the exact repository event, semantic diff, checks, and apply phases behind a business change.
The Apply Timeline is the read-only history of repository work FartherShore observed for a business. Use it to answer four questions: which commit ran, what the compiler thought changed, which environment it targeted, and where the apply stopped.
An entry is derived from platform build and deployment records. You do not create or edit entries with the CLI; a pull request, push, or published GitHub Release creates them.
farthershore apply-timeline list acme --env all --format json
farthershore apply-timeline inspect acme 8f31a42 --env production --format json
inspect accepts an entry id, exact release tag, pull-request number, exact
branch name, or commit-SHA prefix. Matching prefers those forms in that order,
so a release tag remains unambiguous when several releases point at the same
commit.
The environment filter is production, all, or a preview environment name.
Use all when a commit may have run in both preview and production.
Every entry identifies its source, branch, commitSha, optional prNumber,
optional releaseTag, and optional environmentId. It also carries:
semanticDiff: the structural diff, semantic changes, risk summary, and
lifecycle plan computed from the accepted Business program;checks: named projections of build, compile, accept, edge-publish, and
optional billing work;apply: phase status, timestamps, and errors when an apply workflow exists.The top-level status is one of:
| Status | Operator meaning |
|---|---|
pending | Recorded but not started. |
running | At least one phase is still running. |
passed | Validation passed; common for pull requests. It does not mean production is serving the commit. |
applied | The apply published its target snapshot. |
deferred | The contract was accepted but production publication awaits a release boundary. |
failed | A check or phase failed; inspect its summary and error. |
stale | Newer repository work superseded this entry. |
git push
farthershore apply-timeline inspect acme "$(git rev-parse HEAD)" --env all --format json
commitSha and environment to the commit you pushed.running, poll the same selector; do not start a second apply.failed, fix the repository source and push a new commit.deferred, review and publish the production release.applied, confirm the serving state with business status.farthershore business status acme --format json
GitHub checks are useful notification surfaces, but the Apply Timeline is the platform-native record. A green validation entry and a live deployment are different facts; require the expected commit, target environment, and final publish phase.
See Apply and recovery and Production releases.