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

Don't checkout submodules by default #760

Merged
merged 1 commit into from
Sep 4, 2022

Conversation

sdroege
Copy link
Member

@sdroege sdroege commented Sep 3, 2022

This makes sure that cargo does not clone and checkout all the
submodules if pointing to this repository as a git dependency.

To checkout the submodules git submodule update --checkout can be
used.

@sdroege sdroege force-pushed the submodules-update-none branch 2 times, most recently from c270968 to 54232d9 Compare September 3, 2022 16:07
@sdroege
Copy link
Member Author

sdroege commented Sep 3, 2022

Any ideas how this github actions stuff works?

Run actions/checkout@v3
[...]
Adding repository directory to the temporary git global config as a safe directory
/usr/bin/git config --global --add safe.directory /__w/gtk-rs-core/gtk-rs-core
[...]
Run git submodule update --checkout
fatal: unsafe repository ('/__w/gtk-rs-core/gtk-rs-core' is owned by someone else)
To add an exception for this directory, call:

	git config --global --add safe.directory /__w/gtk-rs-core/gtk-rs-core
Error: Process completed with exit code 128.

This makes sure that cargo does not clone and checkout all the
submodules if pointing to this repository as a git dependency.

To checkout the submodules `git submodule update --checkout` can be
used.
@sdroege sdroege merged commit 5dbd381 into gtk-rs:master Sep 4, 2022
@sdroege sdroege deleted the submodules-update-none branch September 4, 2022 17:32
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