Switch submodules to their develop branch #147
Merged
Conversation
This file contains 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
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.
Our documentation currently sources some content from separate repositories, using Git submodules. This is done so that we can include documentation updates together with the respective code changes.
With our current workflow, we are sourcing these files from the
masterbranch of each submodule. This leads to the issue of out-of-synchdevelopbranches and multiple merges frommastertodevelop, which is too complicated, without a clear motivation.After discussing with the rest of the team, we decided it makes sense to just use
developfor the external submodules, dropping the need for the additional merges.