Multirepository project "active branch" not updating - messing with copilot auto commit messages.
I have multiple repositories in one project (instead of opening multiple ide instances - the projects are related).
I have tried using copilot to generate commit messages - including custom instructions. I wanted to make use of extracting ticket id from the branch and autoinsert it to the commit.
However, the branch context seems to get stuck on the one where i last opened some file. Selecting a "directory/repository does not change context.
If i have Project A and Project B, i made changes in A → commit, but i looked at a file in Project B, it thinks the branch is Project B.
Even if there are no changes in B (or i deselected them/not included).
Could it potentially understand what the branch of the changes is according to commit changes state, not IDE state?
Does it have awareness of the commit window at all?
请先登录再写评论。
Hello,
While it strives to be context-aware, its primary focus for commit message generation tends to be on the actively open files and the current IDE's perceived "active branch," which can sometimes get "stuck" on a recently viewed file's repository, even if changes are staged in another. Copilot's awareness of the commit window itself, and specifically which files are staged for a commit across different repositories in a single IDE instance, is not as robust as it could be. This means it may not always infer the correct branch from the staged changes alone, leading to the behavior you're observing.
Regards,
Alison
dogwhistles