Click on the Parable Workspaces icon in the left sidebar of your editor;
Use the List Saved Projects command from the Command Palette.
⌨️ Keyboard Shortcuts
Waiting for implementation...
🛠️ Development
Requirements
- Node.js 22.x+
- VS Code 1.85.0+
Running and Debugging
Open the project in Visual Studio Code.
Install dependencies:
npm install
Press F5 to start a new VS Code instance with the extension enabled.
To debug the Webview:
Open the Parable Workspaces view.
Run the command: Developer: Open Webview Developer Tools from the Command Palette.
To debug the Extension Host:
Check the Debug Console in the main VS Code window for logs and errors.
Set breakpoints directly in the TypeScript files.
Available Commands
Command
Description
npm install
Installs dependencies
npm run build
Compiles the extension
npm run lint
Runs ESLint checks
npm run test
Runs extension tests
npm run package
Packages the extension for distribution
npm run publish
Publishes the extension to VS Code Marketplace
npm run ovsx:publish
Publishes to OpenVSX Registry
Coverage reports are generated in coverage/ and use the nyc tool.
🚀 CI/CD
This project uses GitHub Actions for continuous integration and deployment. The following workflows are configured:
Build Workflow (build.yml)
Trigger: Push to master branch or pull requests
Actions:
Validates conventional commits
Builds and validates the VS Code extension (lint, test, package)
Release Workflow (release.yml)
Trigger: Manual dispatch (workflow_dispatch)
Version auto-detection: The workflow reads commits since the last v* tag and applies semantic versioning rules (breaking change → major, feat: → minor, everything else → patch).
Jobs:
prepare_release — auto-calculates versions, bumps files, updates changelogs, opens a PR targeting master, and creates the v<version> tag
publish_vscode(conditional) — packages and publishes to Visual Studio Marketplace and OpenVSX
create_release(conditional) — creates separate GitHub Releases per plugin and attaches built artifacts
Deploy Landpage Workflow (deploy-landpage.yml)
Trigger: Push to master affecting landpage/**, or manual dispatch
Actions:
Builds and deploys the landing page to Vercel
📦 How to Release
Go to Actions → Release in the GitHub repository.
Click Run workflow.
The workflow will automatically:
Detect the new version from commits since the last release tag using semantic versioning.
Bump versions in package.json.
Update the CHANGELOG.md with commit entries.
Open a release PR with the generated changes targeting master.
Create the v<version> git tag.
Publish to the selected marketplaces.
Create separate GitHub Releases per plugin with built artifacts.
🤝 Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Fork the repository
Create your feature branch (git checkout -b feature/amazing-feature)
Commit your changes (git commit -m 'Add some amazing feature')
Push to the branch (git push origin feature/amazing-feature)
Open a Pull Request
📜 License
This project is licensed under the MIT License - see the LICENSE file for details.
