SCM - The version-control comment is not DevContainer-specific

[Random72IsTaken]

• VS Code Version: 1.69.0 | 92d25e3 | x64
• OS Version: Linux | 5.15.0-40-generic | 43-Ubuntu SMP | x86_64 GNU/Linux

Steps to Reproduce:

1. Install Remote Development extension
2. Set a name for the devcontainer.json
3. Get inside the DevContainer
4. Make a commit comment
5. Switch to another DevContainer with a different name
6. The same comment for the first container is shown here for the 2nd one

I'm assuming that this is not the expected behavior since the name is technically identifying the container...

[chrmarti]

Not sure I understand, do you expect the commit's comment to be different? Could you append screenshots to explain?

[Random72IsTaken]

Yes, I expect them to be different.

One might be working on one dev-container, and has some comments in the source-control section which they had not committed yet. They might switch to another container (with a different name), and wish to start commenting something for version-control too, but they'll not be able to do that without removing the old commit comment for the first project and therefore losing it if they do!

I thought that since every container is identified with its name (or its id), it could be nice to have source-control comments in dev-containers limited down to that identifier or something...

[chrmarti]

You mean the commit comment that you are editing in the SCM viewlet? (Since the comment on a commit is read-only.)

[Random72IsTaken]

[lszomoru]

/gifPlease