Skip to content

fix(vscode): Revert local artifacts workflow-designtime path fix - #9529

Merged
Brian Lam (lambrianmsft) merged 2 commits into
mainfrom
aeldridge/vscode-revert-local-artifacts-fix
Aug 12, 2026
Merged

fix(vscode): Revert local artifacts workflow-designtime path fix#9529
Brian Lam (lambrianmsft) merged 2 commits into
mainfrom
aeldridge/vscode-revert-local-artifacts-fix

Conversation

@andrew-eldridge

@andrew-eldridge Andrew Eldridge (andrew-eldridge) commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Commit Type

  • feature - New functionality
  • fix - Bug fix
  • refactor - Code restructuring without behavior change
  • perf - Performance improvement
  • docs - Documentation update
  • test - Test-related changes
  • chore - Maintenance/tooling

Risk Level

  • Low - Minor changes, limited scope
  • Medium - Moderate changes, some user impact
  • High - Major changes, significant user/system impact

What & Why

The design-time process incorrectly ignores the set ProjectDirectoryPath setting and searches <project root>/workflow-designtime/Artifacts in dynamic list apis. This was previously addressed by creating a symlink at this location to <project root>/Artifacts but this has caused a regression in deploy command due to permissions issues. Reverting the original fix, will take a separate backend fix instead.

Impact of Change

  • Users: Fixes permission error on deploy related to workflow-designtime/Artifacts symlink
  • Developers: N/A
  • System: N/A

Test Plan

  • Unit tests added/updated
  • E2E tests added/updated
  • Manual testing completed
  • Tested in:

Contributors

Andrew Eldridge (@andrew-eldridge)

@andrew-eldridge Andrew Eldridge (andrew-eldridge) added VSCode Issues or PRs specific to VS Code extension risk:medium Medium risk change with potential impact labels Aug 12, 2026
@github-actions

github-actions Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

Revert PR detected — This PR reverts a previously merged fix (title starts with fix(vscode): Revert... and the body states "Reverting the original fix"). Per team policy, revert PRs are automatically approved and exempt from the standard template checks.

PR Title

  • Current: fix(vscode): Revert local artifacts workflow-designtime path fix
  • Issue: None — valid fix: prefix with scope, descriptive.
  • Recommendation: No action needed.

Commit Type

  • Revert PR — template selection not enforced.
  • Note: For future non-revert PRs, remember to check a Commit Type box.

Risk Level

  • Revert PR — auto-passed. For reference, the change removes symlink/junction logic in apps/vs-code-designer (extension distribution), which aligns with the declared risk:medium label and estimate.

What & Why

  • Current: Clear explanation of the regression (deploy permission issue from the Artifacts symlink) and rationale for reverting.
  • Issue: None.
  • Recommendation: No action needed.

Impact of Change

  • Impact section is filled in (Users/Developers/System).
  • Recommendation:
    • Users: Fixes deploy permission error — no action needed.
    • Developers: N/A.
    • System: N/A.

Test Plan

  • Revert removes the feature code and its associated unit tests (artifacts junction describe block). No test action required for a revert.

Contributors


Screenshots/Videos

  • Not applicable — backend/extension logic change, no visual UI impact.

Summary Table

Section Status Recommendation
Title No action needed
Commit Type Auto-passed (revert)
Risk Level Matches medium estimate
What & Why No action needed
Impact of Change No action needed
Test Plan Auto-passed (revert)
Contributors Credited
Screenshots/Videos Not applicable

✅ This is a revert PR and is automatically approved. Good to merge!


Powered by: Copilot CLI (claude-opus-4.8) | Last updated: Wed, 12 Aug 2026 16:56:20 GMT

@github-actions

Copy link
Copy Markdown
Contributor

📊 Coverage Check

🎉 All changed files have adequate test coverage!

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

Reverts the VS Code design-time Artifacts junction workaround to prevent deployment permission failures.

Changes:

  • Removes Artifacts junction creation.
  • Removes associated mocks and unit tests.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
projectFilesConsistency.ts Removes junction creation logic.
projectFilesConsistency.test.ts Removes junction-specific tests and mocks.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@lambrianmsft
Brian Lam (lambrianmsft) merged commit 9797f6d into main Aug 12, 2026
54 checks passed
@lambrianmsft
Brian Lam (lambrianmsft) deleted the aeldridge/vscode-revert-local-artifacts-fix branch August 12, 2026 17:58
Brian Lam (lambrianmsft) pushed a commit that referenced this pull request Aug 13, 2026
* fix(vscode): Fix invalid vscode settings.json values, codeful project deploy, project path cache (#9525)

* fix invalid vscode settings.json values

* address pr comments

* fix logic app resource tree getApplicationSettings to use project root

* fix(vscode): Revert local artifacts workflow-designtime path fix (#9529)

* Revert "fix(vscode): Fix invalid workflow-designtime artifacts path with symlink (#9501)"

This reverts commit 6c2be79.

* fix function signature

* fix(vscode): Codeful project deploy fix (#9527)

* fix codeful deploy issue (set deploySubpath to root and use zipIgnorePattern)

* revert zipIgnorePattern, update .funcignore for codeful

* add tests for codeful .funcignore changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-validated risk:medium Medium risk change with potential impact VSCode Issues or PRs specific to VS Code extension

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants