Skip to content

Conversation

ypid
Copy link
Contributor

@ypid ypid commented Nov 20, 2024

One could argue that this should even be the default because the submodule is managed by containing repository. If the submodule is dirty, the containing repository is dirty as well. Plus the submodule might very well not be on a branch like master but on a specific git commit and that is fine.

But better not make it the default as it would change the behavior. When submodules annoy clustergit users, they can now use the --skip-submodules argument

ypid added 3 commits November 20, 2024 18:10
One could argue that this should even be the default because the
submodule is managed by containing repository. If the submodule is
dirty, the containing repository is dirty as well. Plus the submodule
might very well not be on a branch like master but on a specific git
commit and that is fine.

But better not make it the default as it would change the behavior. When
submodules annoy clustergit users, they can now use the
--skip-submodules argument
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant