GeezerVison

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Aug 11, 2026 11:05pm

PR Summary

Medium Risk
Touches fork promote/sync reference detection for required env secrets, which gates cross-workspace pushes. The change is narrowly scoped and makes the gate stricter (safer), with solid regression coverage.

Overview
Fixes a silent fork-sync gap where {{ENV}} refs in active advanced/manual fields (e.g. Slack's Channel ID) were never recorded as mapping requirements.

Detection previously shared the resource-id ownership gate (verbatimManual), so rewrite and detect disagreed: the secret was rewritten but never surfaced in Secrets mapping or the required-env sync gate. Env detection now gates on execution only — dormant and condition-hidden fields stay skipped; active manual members are detected. Hand-typed resource ids keep their escape-hatch policy unchanged.

^{Reviewed by Cursor Bugbot for commit 1326701. Configure here.}

Greptile Summary

This PR fixes workspace-fork promotion scanning so environment variables referenced by active advanced-mode fields and their active dependents are treated as required mappings.

• Separates environment-reference execution gating from the user-owned resource-ID policy.
• Continues excluding dormant canonical members and condition-hidden fields.
• Adds regression coverage for explicit and inferred advanced modes, mapped-key rewriting, inactive fields, and resource-ID escape hatches.

Confidence Score: 5/5

The PR appears safe to merge, with the revised reference scan matching canonical execution semantics and no actionable regressions identified.

Active advanced values and their dependents now contribute live environment-variable requirements, while dormant and condition-hidden values remain excluded and manual resource IDs retain their existing escape-hatch behavior.

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Inspect subblock value] --> B{Dormant or condition-hidden?}
  B -- Yes --> C[Do not record ENV reference]
  B -- No --> D[Record ENV reference]
  D --> E{Resolver maps key?}
  E -- Yes --> F[Rewrite to target ENV key]
  E -- No --> G[Add required unmapped reference]
  G --> H[Block promotion until mapped]
  A --> I{User-owned manual resource ID?}
  I -- Yes --> J[Keep resource ID verbatim]

_{Reviews (1): Last reviewed commit: "fix(forks): detect secrets referenced fr..." | Re-trigger Greptile}