You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would be helpful if github had some sort of handling for .gitmodules.
In my case I made forks for all the modules that I use in my project and I refer to them via relative path:
In my project I have 18 submodules, from time to time I want to keep up with the remote/upstream repos, and for that I need to open each of these my 18 forks to see if the upstream is updated.
Github could show if the hash that's part of the repo itself is outdated (eg if a submodule is behind referenced head or references stale/dangling hash, which happens when history gets rewritten, or a repo gets rebased). If the referenced submodule is a fork, github should also show if the fork is behind upstream. In other words, it should show state of the project relation to its submodules in the single place without manual error prone jumping and checking individual projects.
ActionsBuild, test, and automate your deployment pipeline with world-class CI/CDProduct Feedback
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Select Topic Area
Product Feedback
Body
Would be helpful if github had some sort of handling for
.gitmodules
.In my case I made forks for all the modules that I use in my project and I refer to them via relative path:
In my project I have 18 submodules, from time to time I want to keep up with the remote/upstream repos, and for that I need to open each of these my 18 forks to see if the upstream is updated.
Instead of showing contents of
.gitmodules
like this one: https://github.com/microsoft/libHttpClient/blob/main/.gitmodulesit could show these parts of the individual repos:
Github could show if the hash that's part of the repo itself is outdated (eg if a submodule is behind referenced head or references stale/dangling hash, which happens when history gets rewritten, or a repo gets rebased). If the referenced submodule is a fork, github should also show if the fork is behind upstream. In other words, it should show state of the project relation to its submodules in the single place without manual error prone jumping and checking individual projects.
Beta Was this translation helpful? Give feedback.
All reactions