Skip to content

Repo is lost when "Generate commit" is requested #4035

@sergeibbb

Description

@sergeibbb

Description

Tested on 74ad6ec (main)

Steps to reproduce

  1. Add multiple repositories to a workspace
  2. Open "Source control: Changes" view
  3. Click "More Actions..." on one of repositories
  4. Select "Generate commit message with GitLens"

Actual result
Repository selector appears

Expected result
Repository is already know and we go right to the "AI features" dialog.

repo-lost.mp4

GitLens Version

16.2.1

VS Code Version

Version: 1.98.0-insider
Commit: 32a41e158d04c9777522dc567574f2a74b8f2bf9
Date: 2025-02-10T05:04:26.807Z (11 hrs ago)
Electron: 32.2.7
ElectronBuildId: 10660205
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.2.0

Git Version

git version 2.46.0 (mac-os)

Logs, Screenshots, Screen Captures, etc

No response

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions