Skip to content

Bring changes from rnmobile/release-v1.17.0 back to master#18588

Merged
mchowning merged 1 commit intomasterfrom
rnmobile/1.17_squashed_onto_master
Nov 18, 2019
Merged

Bring changes from rnmobile/release-v1.17.0 back to master#18588
mchowning merged 1 commit intomasterfrom
rnmobile/1.17_squashed_onto_master

Conversation

@mchowning
Copy link
Copy Markdown
Contributor

This PR is to bring the changes from the 1.17.0 gutenberg-mobile release back to the master branch. Ideally, we would do this with a PR directly from rnmobile/release-v1.17.0 to master, but it appears that a number of commits from the master branch were pulled into the rnmobile/release-v1.17.0 with different hashes (maybe here), which is causing a PR between those branches to "include" a number of commits that are already on master (with a different hash).

In order to avoid confusion about what changes are being brought in and reduce the risk of messing up the git history with the commits that were not related to the 1.17.0 mobile release, I created this rnmboile/1.17_squashed_onto_master branch by checking out master and then squashing the rnmobile/release-v1.17.0 branch onto it. As you would expect, the diff for merging rnmobile/release-v1.17.0 back to master and the diff for this PR appear to be the same, but the number of commits in this PR is 1 as compared to 124 commits in the PR from rnmobile/release-v1.17.0.

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Mobile App - i.e. Android or iOS Native mobile impl of the block editor. (Note: used in scripts, ping mobile folks to change)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants