Repository navigation
Merge main into devel after the squashed 0.2.0 release - #53
Merged
Merged
Conversation
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
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.
#49 was squash-merged, so
mainholds the 0.2.0 release as one commit thatdeveldoes not contain, and the two histories diverged (devel 36 commits ahead, 1 behind, with the same content). This merge commit brings that commit intodevel; the tree is devel's, unchanged (the two conflicts, the version and the changelog, keep devel's 0.2.1 lines). Merge this with a merge commit, not a squash, and then #52 (develintomain) merges cleanly, also as a merge commit, after which both branches share one history again.