Add submodule update/init to just gen-project - #3
Merged
Conversation
Contributor
|
Collaborator
|
The github actions are set up to do the full checkout, so that's covered either way. It looks like this command does update the submodule selected commit- we want to be able to stick to a specific submodule version to manage our deployments. |
Contributor
Author
Removing the --remote avoids updating the hash. Removing the --merge prevents the command from actually merging the files into the branch. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Small change to make sure the submodule is properly initialized and merged in before the project is built. I'm hopeful this won't mess up the automated doc generation...