County IT wants Copilot instruction files to stay aligned as the SQL Database Project evolves. What practice should they follow?
Select an answer to reveal the explanation.
Short Explanation
Instruction files are part of the project toolkit—check them into the same git shelf as the SQL Database Project so every developer gets the same house rules.
Full Explanation
Versioning Copilot instruction files in source control with the SQL Database Project is the practice county IT should follow so instructions stay aligned as the project evolves. Keeping instructions beside the municipal SQL code makes standards reviewable in PRs, consistent across branches, and recoverable when policy changes.
Keeping instruction files only on one analyst’s laptop outside git fails by concept because that creates a single point of failure and drift. Emailing a new instruction file as an unsigned attachment each sprint with no history fails because it lacks version history, integrity, and review. Storing instructions solely inside production database extended properties fails because production is the wrong control plane for developer AI standards and bypasses normal source-control collaboration.
Exam caveat: Treat Copilot instruction files as project artifacts under the same change control as the SQL Database Project. Laptop-only copies, unsigned email drops, and production-only storage undermine municipal collaboration.
Operational check: Add instruction files to the county SQL Database Project repo, require PR review for instruction changes, verify new developers receive them via clone—not email—and periodically diff instructions against current civic coding policy.