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
As the managed dictionaries are stored as stubs on git, they are not registered as changed files when a new version is checked out (e.g. pull from remote). This means that the user will still have the old version on disk. We need to trigger the change somehow.
Possible workarounds:
use a git post-checkout hook to rewrite the file (fragile and will mark the file as modified)
add a unique marker to the stub (e.g. the file hash) so that git sees it as changed (will potentially cause merge conflicts)
The text was updated successfully, but these errors were encountered:
As the managed dictionaries are stored as stubs on git, they are not registered as changed files when a new version is checked out (e.g. pull from remote). This means that the user will still have the old version on disk. We need to trigger the change somehow.
Possible workarounds:
use a git post-checkout hook to rewrite the file (fragile and will mark the file as modified)
add a unique marker to the stub (e.g. the file hash) so that git sees it as changed (will potentially cause merge conflicts)
The text was updated successfully, but these errors were encountered: