Git worktree support tools

[lsierant]

Based on PR #850

Chain of upstream PRs as of 2026-03-03

• PR Commit .idea files and run configurations #850:
  master ← lsierant/intellij-settings-only

  • PR Git worktree support tools #693 (THIS ONE):
    lsierant/intellij-settings-only ← lsierant/intellij-settings

Summary

Tooling necessary to work effectively on multiple worktrees in parallel.

Requirements for perfect tooling for working with worktrees

• you create new worktree as easy as creating a branch (one command)
• created worktree is ready to go: context switching works, it's fully isolated from other worktrees, IDE opened from it is fully configured (operator and e2e tests works without any additional configuration)
• it's easy to switch between worktrees (no need to regenerate contexts, sourcing venvs, etc.)

The tooling in this PR solves most of those:

• setup_git_worktree script creates fully configured worktree with one command
• mck cd alias allows to navigate easily between worktrees with automatic context sourcing
• comitted run configurations and .idea files makes the IDE almost configured. Unfortunately some manual configuration is still needed in the new worktree.

What's still missing:

• full isolation
• creating new evg hosts for full runtime isolation
• local operator is still clashing on the same ports when running more than one at a time
• kubefwd, evg_host.sh tunnel is still not isolated per worktree

Changes

• scripts/dev/setup_git_worktree.sh <branch name> - checks out new worktree in $PROJECT_DIR/../
  • automatically creates new venv
  • copies private-context and .generated/.current_context
• scripts/aliases/mck_aliases - aliases to help switching between worktrees, with automatic context and venv sourcing
• adds IntelliJ run configurations so after worktree creation and openining new IDE instance, there is very little manual configuration needed to have fully configured IDE

mck aliases

mck cd - worktree switcher

mck switch - wrapper over make switch, but it's automatically sourcing the generated envs afterwards

[github-actions]

⚠️ (this preview might not be accurate if the PR is not rebased on current master branch)

MCK 1.7.1 Release Notes

Other Changes

• Container images: Merged the init-database and init-appdb init container images into a single init-database image. The init-appdb image will no longer be published and does not affect existing deployments.