Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(readme): explain handling of git submodules (DEV-1502) #256

merged 4 commits into from Nov 17, 2022


Copy link

resolves DEV-1502

@jnussbaum jnussbaum self-assigned this Nov 16, 2022 Outdated Show resolved Hide resolved Outdated Show resolved Hide resolved
Copy link

@BalduinLandolt BalduinLandolt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The joys of submodules...
Personally I tend to refrain from working in the submodule, I much rather use it only to include the latest stage, but work in the repo of the submodule itself. But I suppose that wouldn't work nicely for your use case.

Co-authored-by: irinaschubert <>
@jnussbaum jnussbaum merged commit 1dc8483 into main Nov 17, 2022
4 checks passed
@jnussbaum jnussbaum deleted the wip/dev-1502-explain-git-submodules branch November 17, 2022 11:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

None yet

3 participants