Skip to content

removal of LLM instructions deployment logic#3126

Open
languy wants to merge 8 commits into
mainfrom
dev/languy/remove-llminstructions-deploy-logic
Open

removal of LLM instructions deployment logic#3126
languy wants to merge 8 commits into
mainfrom
dev/languy/remove-llminstructions-deploy-logic

Conversation

@languy

@languy languy commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Remove logic and setting for deploying or removing LLM instructions.
Remove LLM instructions if the md5 hash match the original instructions that were deployed and remove deployment manifest from global storage.
Fixes #3125.

@languy languy marked this pull request as ready for review June 5, 2026 08:19
@languy languy requested a review from a team as a code owner June 5, 2026 08:19
bk201-
bk201- previously approved these changes Jun 5, 2026
@sevoku

sevoku commented Jun 8, 2026

Copy link
Copy Markdown
Member

@copilot backport this PR to rel/0.34

Copilot AI commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

@copilot backport this PR to rel/0.34

I couldn’t run the backport flow because gh auth status failed in the agent (GITHUB_TOKEN is invalid). Please refresh agent GitHub auth/re-run the task, and I can backport this PR to rel/0.34 immediately.

Copilot finished work on behalf of sevoku June 8, 2026 20:11
Copilot AI requested a review from sevoku June 8, 2026 20:11
sevoku added a commit that referenced this pull request Jun 8, 2026
…gent

The Phase A 'abort if gh unauthenticated' gate caused the GitHub.com cloud
agent to bail out of a backport before doing any git work when 'gh auth
status' reported GITHUB_TOKEN invalid (see #3126).

In the cloud agent, git push auth comes from the platform credential helper
and the PR is opened by the platform - neither needs gh. Add a cloud-agent
override so a failing 'gh auth status' no longer stops the backport; only
PR-metadata edits need gh, with GH_TOKEN retry and REST API fallbacks.
Copilot AI changed the title refactor: remove LLM instructions deployment logic and related assets [rel/0.34] Backport removal of LLM instructions deployment logic Jun 8, 2026
Copilot finished work on behalf of sevoku June 8, 2026 20:25
sevoku
sevoku previously approved these changes Jun 8, 2026

@sevoku sevoku left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the Copilot noise, I was hoping the backport agent would work now, but it doesn't as expected.

@sevoku sevoku changed the title [rel/0.34] Backport removal of LLM instructions deployment logic removal of LLM instructions deployment logic Jun 8, 2026
sevoku added a commit that referenced this pull request Jun 9, 2026
* fix(skill): harden backport branch naming and PR body authoring

Addresses issues seen in rel/0.34 backport PRs (#3133-#3135):
- Branch slug now replaces every '/' in the target (rel/0.34 -> rel-0.34);
  PR #3133 produced backport/3036-to-rel/0.34 with the slash left in.
- PR body must be passed via --body-file, never inline --body, which mangled
  descriptions and printed literal newline escape sequences verbatim.
- Forbid task-list checkboxes in the PR body (GitHub renders them as a
  misleading 'N tasks done / Progress 100%' bar).
- Do not hard-wrap body sentences; re-flow copied descriptions.
- Clarify branch prefix: backport/ for local runs, copilot/ only for the
  GitHub.com cloud agent.

* fix(skill): don't abort backport on gh auth status failure in cloud agent

The Phase A 'abort if gh unauthenticated' gate caused the GitHub.com cloud
agent to bail out of a backport before doing any git work when 'gh auth
status' reported GITHUB_TOKEN invalid (see #3126).

In the cloud agent, git push auth comes from the platform credential helper
and the PR is opened by the platform - neither needs gh. Add a cloud-agent
override so a failing 'gh auth status' no longer stops the backport; only
PR-metadata edits need gh, with GH_TOKEN retry and REST API fallbacks.

* fix(skill): address PR review on body-file portability and newline rationale

- Make the body-file example cross-platform (TMPDIR/$env:TEMP) and keep it
  outside the repo so it can't be accidentally staged; add a cleanup note.
- Correct the hard-wrap rationale: scope it to PR descriptions/comments
  (where GitHub honors single newlines as hard breaks, unlike rendered .md
  files) and add the noisy-diff / plaintext-preview reasons.
@languy languy dismissed stale reviews from sevoku and bk201- via 2f30787 June 10, 2026 13:39
@github-actions

github-actions Bot commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

🎉 Build Summary

🔗 Source

📦 Package Information

🧪 Test Results

  • Unit Tests: ✅ success
  • Integration Tests: ✅ success

✅ Build Status

All checks completed successfully!

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR removes the extension’s LLM instruction file deployment/removal surface area (commands + setting) and replaces it with a best-effort activation-time cleanup to delete previously deployed instruction files when they are unmodified, aligning with issue #3125 (remove LLM asset management setting from VS Code Settings).

Changes:

  • Removed the cosmosDB.manageLLMAssets contributed setting and the cosmosDB.ai.deployInstructionFiles / cosmosDB.ai.removeInstructionFiles commands.
  • Deleted the old deployment/removal implementation and its tests; added a new activation-time cleanup (cleanupLLMInstructionsFiles) that deletes the legacy instructions file only when its MD5 matches the known original and clears the obsolete manifest key.
  • Updated localization bundle entries and updated package-lock.json.

Reviewed changes

Copilot reviewed 7 out of 9 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
src/extension.ts Stops deploying instruction files on activation; adds activation-time cleanup call.
src/cosmosdb/commands/deployLLMInstructionsFiles.ts Removes legacy deploy/remove logic (deleted).
src/cosmosdb/commands/deployLLMInstructionsFiles.test.ts Removes tests for legacy deploy/remove logic (deleted).
src/cosmosdb/commands/cleanupLLMInstructionsFiles.ts Adds new best-effort cleanup logic + telemetry.
src/commands/registerCommands.ts Removes registration of LLM assets commands.
package.json Removes LLM commands and the cosmosDB.manageLLMAssets configuration contribution.
package-lock.json Updates lockfile (notably removes libc fields from multiple native/binary packages).
l10n/bundle.l10n.json Removes now-unused localized strings for the deleted feature.
resources/llm-assets/.gitkeep Keeps the (now-empty) llm-assets folder in the repo.

Comment thread src/cosmosdb/commands/cleanupLLMInstructionsFiles.ts
Comment thread src/cosmosdb/commands/cleanupLLMInstructionsFiles.ts Outdated
Comment thread src/cosmosdb/commands/cleanupLLMInstructionsFiles.ts Outdated
Comment thread l10n/bundle.l10n.json
bk201-
bk201- previously approved these changes Jun 11, 2026
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
languy and others added 2 commits June 11, 2026 16:28
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
@mkrueger

Copy link
Copy Markdown
Member

Format checks fail for me all the time too :/ - how about using an auto formatter on checkin?

@github-actions

github-actions Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

🎭 E2E Tests (Playwright + VS Code)

Commit: a9df80c
Pull Request: #3126 removal of LLM instructions deployment logic

🧪 Result

  • E2E Tests: ✅ success

📥 Artifacts (run)

Tip: the HTML report artifact contains a self-contained Playwright report.
Download the zip, extract, and open index.html — or run
npx playwright show-report <extracted-dir> for the interactive view.

@github-actions

Copy link
Copy Markdown
Contributor

🔨 Build, Lint & Test

🔗 Source

📦 Package Information

🧪 Test Results

  • Unit Tests: ✅ success
  • Integration Tests (extension host): ✅ success

📥 Artifacts (run)

✅ Build Status

Build and local tests passed. See sibling comments below for E2E and NoSQL integration results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove LLM assets settings from extension settings

6 participants