The current placement of the Submodules section makes it easy to overlook when working with repositories that contain Git submodules.
Submodules are an important part of the repository structure, similar to branches, remotes, and tags. However, because the section is displayed after areas like Stashes, it is not always noticed by users.
A possible improvement would be moving Submodules to a more prominent location, closer to other repository structure elements, for example:
- Branches
- Remotes
- Tags
- Submodules
- Stashes
or giving Submodules a more visible dedicated section/icon.
The goal is not only aesthetics: missing a submodule can lead to confusion when changes, updates, or synchronization problems happen. Developers may not realize that part of the repository is managed separately.
Making Submodules easier to discover would improve the experience for projects that rely on shared repositories and Git submodule workflows.
The current placement of the Submodules section makes it easy to overlook when working with repositories that contain Git submodules.
Submodules are an important part of the repository structure, similar to branches, remotes, and tags. However, because the section is displayed after areas like Stashes, it is not always noticed by users.
A possible improvement would be moving Submodules to a more prominent location, closer to other repository structure elements, for example:
or giving Submodules a more visible dedicated section/icon.
The goal is not only aesthetics: missing a submodule can lead to confusion when changes, updates, or synchronization problems happen. Developers may not realize that part of the repository is managed separately.
Making Submodules easier to discover would improve the experience for projects that rely on shared repositories and Git submodule workflows.