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
{{ message }}
Repository navigation
Dry run of a submodule update lists an excluded submodule as one to nest #230
I used 1.2.2 for the next tdesktop sync, and it worked: 11 upstream commits, three nested repos pulled, no conflicts.
I found one minor problem
Version: git-nested 1.2.2, git 2.56.1, macOS.
Setup: a fork of tdesktop, with submodules init --recursive. QuickJS is nested at Telegram/ThirdParty/widget-sandbox/packages/ios/Sources/CQuickJS/quickjs.
We do not want its test262 submodule, so its .gitnested has:
submodules: nestexclude:
- test262
Command: in the fork, origin is the tdesktop upstream. An update from tdesktop 346f10f to bf4f714. This moves quickjs to fbc91d85432b.
git nested submodules update --dry-run origin/dev
Actual:
would merge 11 commits of origin/dev
Telegram/ThirdParty/twidget: would pull to 866f0971e7cc
Telegram/ThirdParty/widget-sandbox: would pull to a6cf612b9bab
Telegram/ThirdParty/widget-sandbox/packages/ios/Sources/CQuickJS/quickjs: would pull to fbc91d85432b
Telegram/ThirdParty/widget-sandbox/packages/ios/Sources/CQuickJS/quickjs/test262: would nest at 5ef1e5723be9
Expected: no test262 line.
The real update follows exclude and does not nest test262.
Activity