Files

busya 8c10632494 feat(semantic): curator-driven protocol hardening — decision memory + relation repair

- Add @RATIONALE/@REJECTED to 103+ C4/C5 contracts across backend core, services, API routes, and frontend models
- Fix 109 unresolved @RELATION edges (Auth.*, SupersetClient.*, AgentChat.*, ADR cross-refs)
- Add 13 @ingroup tags for DSA/HCA attention grouping
- Repair 29 stale graph edges via index rebuild
- Update .kilo agent prompts and skills for GRACE-Poly v2.6 compliance
- Git integration: merge routes, branch lifecycle, remote providers, UX components
- 0 broken anchor pairs, index rebuilt with 0 parse warnings

2026-07-02 08:53:19 +03:00

3.3 KiB

Raw Blame History

Quickstart: Git Integration for Dashboards

Last Updated: 2026-07-01 Audience: BI developers and Superset analysts.

Prerequisites

A running Superset instance.
A Git repository (GitLab, GitHub, etc.) created for your dashboard.
A Personal Access Token (PAT) with repo scope.

Setup Guide

1. Configure Git Connection

Navigate to Git in the operations menu.
Open Settings -> Git if no Git server is configured.
Enter your Git Provider details:
- Repo URL: https://github.com/myorg/sales-dashboard.git
- Username: myuser
- PAT: ghp_xxxxxxxxxxxx
Test and save the connection.

2. Connect a Dashboard Repository

Open Git -> Управление Git.
Select a dashboard and click Управление Git.
If the dashboard has no repository, choose one of two paths:
- Create new repository: create a remote repository on the selected Git server.
- Connect existing repository: bind a known remote URL to the dashboard.
Confirm the setup summary before initialization:
- Git server
- Repository URL
- Default production branch: prod
- Environment branches: dev, preprod, prod
After initialization, sync the current Superset dashboard into the repository.

Branch Model

The primary dashboard lifecycle is:

dev -> preprod -> prod

dev: active dashboard development.
preprod: validation before production.
prod: production-ready state.
Existing repositories with main or master remain supported as legacy refs, but new repositories should use prod.

Planned branch extensions:

feature/*: created from dev, merged back into dev.
hotfix/*: created from prod, merged into prod and dev.

Development Workflow

Making Changes

Edit your dashboard in Superset as usual.
Open the dashboard in Git Management.
Click Sync from Superset. This exports the current dashboard and unpacks it into the local Git repository.
Review the change summary and raw YAML diff.

Saving a Version

Enter a clear change description or generate one.
Click Save version (Commit).
Optionally send the commit to the remote server (Push).

Publishing Through Environments

Work in dev.
Promote dev -> preprod through a Merge Request when ready for validation.
Promote preprod -> prod through a Merge Request after approval.
Deploy to Superset production only from prod.

Branching

For parallel work, create a branch named like feature/q4-updates from dev.
Keep environment branches (dev, preprod, prod) protected from accidental deletion.
Treat main, master, and origin/* as legacy or advanced refs in the UI.

Deploying

Open Publish to environment.
Select the target environment.
For PROD, verify the confirmation summary: dashboard name, source branch, target environment, last commit, author, and changed files.
Confirm deploy. The current repository state will be imported into the target Superset environment.

Implementation Status (2026-07-01)

The target workflow is dev -> preprod -> prod. Phase 12A remediation replaced new-repository main defaults with prod, updated release UI labels, and keeps existing main/master repositories as legacy-compatible refs.

3.3 KiB Raw Blame History