Home's span card leads with What changed (#53): Summarize, the plain-English account of what changed, why and what is live, sat under People, below a list of counts, though it is what most people open Home for. It now comes first in the span's card, under its heading, with People and then Landed below it. The Home guide says What changed is at the top of the card and People under it. #368 · flagon-io/g1t

check: `actions/checkout` checks out from g1t.

check: `actions/cache/restore`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

plan: `actions/checkout` checks out from g1t.

plan: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.

migrate: `actions/checkout` checks out from g1t.

migrate: `actions/cache/restore`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

migrate: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.

core: `actions/checkout` checks out from g1t.

core: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

core: `actions/cache/restore`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

core: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

core: `actions/cache/restore`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

core: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.

edge: `actions/checkout` checks out from g1t.

edge: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

edge: `actions/cache/restore`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

edge: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

edge: `actions/cache/restore`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

edge: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.

front: `actions/checkout` checks out from g1t.

front: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

front: `actions/cache/restore`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

front: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

front: `actions/cache/restore`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.

front: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.

smoke: `actions/checkout` checks out from g1t.

unit	stage	action	live	why
events	core		89ee2f7	nothing it is built from changed
identity	core		89ee2f7	nothing it is built from changed
repos	core		89ee2f7	nothing it is built from changed
work	core		89ee2f7	nothing it is built from changed
search	core		89ee2f7	nothing it is built from changed
projects	core		304b02c	nothing it is built from changed
chat	core		304b02c	nothing it is built from changed
artifacts	core		304b02c	nothing it is built from changed
telemetry	core		304b02c	nothing it is built from changed
notify	core		304b02c	nothing it is built from changed
billing	core		89ee2f7	nothing it is built from changed
integrations	core		304b02c	nothing it is built from changed
webhooks	core		89ee2f7	nothing it is built from changed
actions	core		89ee2f7	nothing it is built from changed
packages	core		89ee2f7	nothing it is built from changed
security	core		89ee2f7	nothing it is built from changed
deployments	core		304b02c	nothing it is built from changed
runner	core		304b02c	nothing it is built from changed
og	core		304b02c	nothing it is built from changed
api	edge		89ee2f7	nothing it is built from changed
pages	edge		2a24415	nothing it is built from changed
status	edge		304b02c	nothing it is built from changed
web	front	deploy	304b02c	1 changed file (apps/web/app/routes/workspace/home.tsx)
sudo	front		304b02c	nothing it is built from changed
docs	front	deploy	304b02c	1 changed file (apps/docs/src/content/docs/guides/home.md)

flagon-io/g1t

Deploy plan for 5c0bf5d