GreenLane · Lane board

GreenLane is an AI release lane for GitLab: it runs only the CI jobs a change needs, repairs a failed pipeline on its own, deploys without a stored key, and tells you what every run cost. This board is that record, one row per merge request, built from the project's public pipelines.

← Lane board

!10 Plan: Lane Scout meets a new issue with a forecast and a carbon budget merged · by yy5652-hash · 2026-10-18 17:23 UTC · on GitLab

latest child pipeline 2960641680 · success · 4 pipelines on this merge request

7 of 9 GitLab DevSecOps stages with evidence for this merge request

lit: evidence for the merge request, click it ran and failed no evidence

plan
the merge request closes no issue
create
!10, opened by yy5652-hash 2026-10-18 17:23 UTC
5 commits by people 2026-10-18 18:05 UTC
verify
lint-api · test-api · build-web · docs-links · flow-lint 2026-10-18 18:11 UTC
package
build-image 2026-10-18 18:11 UTC
secure
secret-detection · sast · dependency-scan · iac-scan · container-scan 2026-10-18 18:11 UTC
release
deploy-review, staged at mr-10---greenlane-demo-37vmav4mla-lz.a.run.app 2026-10-18 18:11 UTC
deploy-cloud-run on the default branch 2026-10-18 18:14 UTC
configure
config-drift on the default branch 2026-10-18 18:14 UTC
monitor
scheduled monitor passed after the deploy, pipeline 2960667762 2026-10-18 18:25 UTC
govern
govern was not in the lane yet

The jobs of the latest pipeline

lint-api
11 s
test-api
12 s
build-web
8 s
docs-links
9 s
flow-lint
11 s
secret-detection
17 s
sast
19 s
dependency-scan
28 s
iac-scan
15 s
build-image
40 s
container-scan
31 s
deploy-review
40 s

ran skipped failed fixed by the Lane Mechanic · width by the seconds the note charged, never narrower than its name

12 of 12jobs run
241 sinstead of about 241 s
+12 %CO2e: 0.386 g against 0.346 g

Staging

https://mr-10---greenlane-demo-37vmav4mla-lz.a.run.app: this merge request's image as its own Cloud Run revision with no production traffic, checked with real requests by deploy-review. The address was taken down when the merge request was merged.

What happened, to the second (UTC, 2026-10-18)

Every point is a commit or a pipeline from the public API; the person's commits are white, the Lane Mechanic's green.

The agents

Lane Steward read the real diff, the pipeline and the job logs and posted its verdict on the merge request.

The carbon note, from the carbon-account job

jobransecondsg CO2ewhy
build-imageyes400.057Dockerfile (infra); services/api/app.py (api)
build-webyes80.011full run
container-scanyes310.044Dockerfile (infra); services/api/app.py (api)
dependency-scanyes280.040full run
deploy-reviewyes400.057follows build-image
docs-linksyes90.013README.md (docs); docs/how-it-works.md (docs)
flow-lintyes110.016flows/lane-scout.yml (flows)
iac-scanyes150.021Dockerfile (infra)
lint-apiyes110.016services/api/app.py (api); services/api/mcp.py (api)
sastyes190.027services/api/app.py (api); services/api/mcp.py (api)
secret-detectionyes170.024always runs
test-apiyes120.017services/api/app.py (api); services/api/mcp.py (api)

the job log · the summary line: This pipeline: 0.386 g CO2e. Running everything would have been about 0.346 g, so about -12 % was avoided (0 runner-seconds).