Skip to content

Smoke test workspace_swap + chat-driven confirmation in prompt #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
michaeldeongreen merged 2 commits into from
May 9, 2026
Merged

Smoke test workspace_swap + chat-driven confirmation in prompt #35

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e0ba1c5
Swap to feature workspace + chat-driven confirmation in prompt
michaeldeongreen May 9, 2026
30d38bb
Swap back to dev for PR readiness
michaeldeongreen May 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions .github/prompts/swap-to-feature.prompt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,15 @@
description: Swap the repo's IDs to your feature workspace and create the value set for the current branch.
mode: agent
---
Run `python scripts/workspace_swap.py` from the repo root and report the output to me. The script will rewrite tracked Fabric files (semantic model, notebooks) so they point at your feature workspace instead of dev, create a feature value set, and update settings.json. It reads the feature workspace and lakehouse GUIDs from `.env` at the repo root — if `.env` is missing or empty, it will fall back to an interactive prompt.
The script `scripts/workspace_swap.py` rewrites tracked Fabric files (semantic model, notebooks) so they point at your feature workspace instead of dev, creates a feature value set, and updates settings.json. It reads `FEATURE_WORKSPACE_ID` and `FEATURE_LAKEHOUSE_ID` from `.env` at the repo root and asks for a `YES` confirmation before applying. When invoked through this prompt, that confirmation must happen here in chat — never in the terminal — to avoid live-prompt handling problems.

After the script finishes, summarize what changed and remind me to commit and push the changes, then sync the workspace from the Fabric UI.
Follow this exact sequence:

1. Read `.env` at the repo root and read the dev workspace + lakehouse IDs from `data/fabric/Patterns_Variables.VariableLibrary/variables.json`.
2. Show me the planned swap in chat (current branch, dev → feature workspace ID, dev → feature lakehouse ID).
3. Use the chat UI to ask me a single question with two options: `YES` and `NO` (uppercase, exact). Do not proceed until I answer.
4. If I answer `YES`, run `echo "YES" | python scripts/workspace_swap.py`. The piped `YES` satisfies the script's confirmation gate non-interactively, so the terminal never blocks. Report the full output.
5. If I answer `NO`, do nothing further and confirm in chat that the swap was not applied.
6. After a successful run only, summarize what changed and remind me to commit and push the changes, then sync the workspace from the Fabric UI.

Do not run the script directly without piping `YES` (it will block on the terminal prompt). Do not skip the chat confirmation — the in-script confirmation is bypassed by the pipe and the chat dialog is the gate.