Browse and manage SQL scripts imported from the workspace repository; scripts are reusable building blocks referenced by pipelines via INCLUDE SCRIPT.
## Overview The Scripts page lists the SQL scripts registered in the catalog. Scripts are registered exclusively by scanning the workspace's git repository: any .sql file that carries no PIPELINE declaration is imported as a script. The workspace is managed by editing files in git and rescanning; DeltaForge does not author workspace content, so there is no create-script button. The page is for browsing, inspecting, governing, and removing the scripts the scan has imported. Scripts are imported references, not executable jobs. They serve as building blocks that pipelines pull in through the INCLUDE SCRIPT directive, so the page shows registry columns (name, file path, status, approval, version, updated) and carries no run counts, success rates, or duration statistics; execution metrics belong to pipelines. ## Key Features - **Repository-scanned registry.** Every row corresponds to a .sql file discovered by the workspace repository scan. The git file is the source of truth: a rescan refreshes the catalog copy (content and version) from the repository. - **Dependency tracking (INCLUDE SCRIPT).** The page detects INCLUDE SCRIPT directives within a script and displays a dependency tree showing which other scripts are referenced, which helps trace the inclusion chain and avoid circular dependencies. - **Script expansion preview.** Preview the fully expanded SQL that results from resolving all INCLUDE SCRIPT directives, in the order it would run inside a pipeline. - **Catalog metadata editing.** Edit governance-level fields on the catalog entry: display name, description, status (active or deprecated), approval status, and the production flag. Content shown in the detail panel comes from the imported file; lasting content changes belong in the git repository, since the next scan refreshes the catalog copy from the file. - **Deletion with persisted import exclusion.** Deleting a script removes the catalog entry and records the source file in the repository's import exclusions, so the next scan (manual, refresh, or the pull-and-rescan sync) does not re-import it. The .sql file itself stays untouched in git; re-selecting it in the workspace scan wizard clears the exclusion and imports it again. ## Workflow 1. Author or change script files in the workspace's git repository and run the repository scan from the workspace page; files without a PIPELINE declaration appear here as scripts. 2. Navigate to the Scripts page from the Workflow sidebar and locate a script by name, alias, or file path. 3. Select a script to inspect its content, dependency tree, and expansion preview. 4. Adjust catalog metadata (status, approval, production flag) as the script moves through governance. 5. Delete scripts that should no longer be part of the catalog; the file remains in git but is excluded from future scans until re-selected in the scan wizard.