Skip to content

#2049: Add initial calm workspace commands #2110

Open
willosborne wants to merge 34 commits intofinos:mainfrom
willosborne:bundle-file-loader
Open

#2049: Add initial calm workspace commands #2110
willosborne wants to merge 34 commits intofinos:mainfrom
willosborne:bundle-file-loader

Conversation

@willosborne
Copy link
Member

@willosborne willosborne commented Feb 5, 2026

Description

Adds the initial commands described in #2049 for managing workspaces.

  • Creating: calm workspace init
  • switching between them: calm workspace switch
  • adding files to them: calm workspace add
  • deleting them: calm workspace clean
  • visualising them: calm workspace tree, calm workspace list and calm workspace show

Type of Change

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📚 Documentation update
  • 🎨 Code style/formatting changes
  • ♻️ Refactoring (no functional changes)
  • ⚡ Performance improvements
  • ✅ Test additions or updates
  • 🔧 Chore (maintenance, dependencies, CI, etc.)

Affected Components

  • CLI (cli/)
  • Shared (shared/)
  • CALM Widgets (calm-widgets/)
  • CALM Hub (calm-hub/)
  • CALM Hub UI (calm-hub-ui/)
  • Documentation (docs/)
  • VS Code Extension (calm-plugins/vscode/)
  • Dependencies
  • CI/CD

Commit Message Format ✅

Testing

  • I have tested my changes locally
  • I have added/updated unit tests
  • All existing tests pass

Checklist

  • My commits follow the conventional commit format
  • I have updated documentation if necessary
  • I have added tests for my changes (if applicable)
  • My changes follow the project's coding standards

Copy link
Member Author

Choose a reason for hiding this comment

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

Need to delete this, and probably move it to an issue

@willosborne
Copy link
Member Author

need to look at why so many things are failing on this pr

@markscott-ms markscott-ms marked this pull request as draft February 5, 2026 17:33
@rocketstack-matt
Copy link
Member

@willosborne the build failures are caused because you're using Node 25 locally and our configured builds use Node 22

@willosborne
Copy link
Member Author

@rocketstack-matt fixed, bad lockfile from macOS build got checked in

@willosborne willosborne self-assigned this Feb 16, 2026
@willosborne willosborne marked this pull request as ready for review February 16, 2026 17:05
Copy link
Member

@rocketstack-matt rocketstack-matt left a comment

Choose a reason for hiding this comment

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

There are a few areas that could be improved, I'm ok for them to be done in a later PR if you're happy with them.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants