workspace

README

WS

No hassle DX to manage dozen of microservices at work.

• WS
  • Install
  • Project Tracking
  • Run Tests
  • Git Cleanup
  • Worktrees and DB Migrations
  • Development

Install

Homebrew:

smth on elvish

Go way:

go install github.com/andrew-malikov/workspace@latest

i.e. not ready yet.

Project Tracking

First thing to do is to set up the microservice you intend to run locally or to check whether integration/ component tests are indeed green. It gets handy when you do, see the in the next chapter.

Add a new directory with a microservice into the tracker:

ws track <alias> [directory]

Remove already tracked directory from the tracker:

ws untrack [directory | alias]

Run Tests

There are three types of tests

• unit
• integration
• component

Unit tests don't require any prior setup in opposite to the rest that do require to up docker compose. Usually it's no big deal BUT gotcha bangs you quick when you try to up several composes, ports are the same (of some services unfortunately) so running it all doesn't work out. So what you do is dancing with previous composes you touched.

OR you can use this one:

ws tests [-a alias]

It would check whether any other compose is up (across tracked ones) and down it.

Git Cleanup

Lots of people make lots of code and thus lots of stale branches (me too by the way). Prints the stale branches to clean up (only author's branches):

ws git cleanup --dry-run

| [ ] | branch           | author | updated at          | status |
| --- | ---------------- | ------ | ------------------- | ------ |
| [ ] | feat/glancy-list | you    | 2026-08-02 11:30 AM | synced |
| [x] | feat/remove-me   | you    | 2026-02-01 14:15 PM | local  |
| ... | ...              | ...    | ...                 | ...    |
| [x] | story/mocks      | you    | 2024-31-12 23:59 PM | remote |

You can count your teammates:

ws git cleanup --dry-run --team

| [ ] | branch           | author       | updated at          | status |
| --- | ---------------- | ------------ | ------------------- | ------ |
| [ ] | feat/glancy-list | you          | 2026-08-02 11:30 AM | synced |
| [x] | feat/remove-me   | you          | 2026-02-01 14:15 PM | local  |
| ... | ...              | ...          | ...                 | ...    |
| [x] | hotfix/your-pc   | mr. anderson | 2021-01-01 00:00 AM | local  |

Running without --dry forces the show up plan first for you to review and then if you're okay execute:

ws git cleanup

The good part it spit out when the last commit was made and who's the author, which makes easier to communicate whether the branch is indeed stale.

Worktrees and DB Migrations

Worktree support isn't in the current roadmap BUT I definitely would work on it as it would allow tracking mismatched DB migrations. Basically migrations get messed up when several people work on the same mircoservice and have their own new migrations, the apply order guaranteed only by who deploys first. The idea is to check across all the branches that the order is preserved against the current work branch.

Development

Build:

mise build

Run:

./binaries/ws

Debug:

dlv exec binaries/ws