Create Repository Workspaces from the EWM VS Code Extension

Teams increasingly use the IBM EWM extension for Microsoft Visual Studio Code as their primary development environment. To fully adopt VS Code, users need access to the same essential SCM capabilities available in the traditional Eclipse-based client.

Problem:

It is currently not possible to create a Repository Workspace directly from the EWM VS Code extension. Users must switch to the Eclipse client to perform this mandatory SCM task, creating a dependency on an additional tool.

Impact:

This limitation prevents some teams from working exclusively in VS Code, complicates onboarding, and forces users to maintain and learn the Eclipse client for a basic SCM operation.

Goal of the Idea:

Allow users to create and manage Repository Workspaces directly from the EWM VS Code extension.

Why is it Useful?:

Removes dependency on the Eclipse client.

Improves developer productivity and onboarding.

Supports a modern VS Code-centric development experience.

Increases adoption of the EWM VS Code extension.

Provides a seamless environment for leveraging Bob and other AI assistants within VS Code, eliminating workflow disruptions caused by having to switch to the Eclipse client for repository workspace creation.

How Should it Work?:

Provide a Create Repository Workspace action within the VS Code extension, allowing users to create a workspace from a stream, component, or existing repository workspace, with options similar to those available in the Eclipse client.