Skip to content

Conversation

@flarnie
Copy link
Contributor

@flarnie flarnie commented May 3, 2017

what is the change?:
This seems useful, even for this short-lived branch, and some commits we
cherry-picked were making updates to it. So we just pulled the fixture
in from master.

why make this change?:
To bring things into a bit more consistency with master.

test plan:
Manually tested the fixture - things seem to work.

issue:
None - but related to cherry-picking
#9584

**what is the change?:**
This seems useful, even for this short-lived branch, and some commits we
cherry-picked were making updates to it. So we just pulled the fixture
in from master.

**why make this change?:**
To bring things into a bit more consistency with master.

**test plan:**
Manually tested the fixture - things seem to work.

**issue:**
None - but related to cherry-picking
facebook#9584
@flarnie flarnie added this to the 15.6 milestone May 3, 2017
@flarnie
Copy link
Contributor Author

flarnie commented May 9, 2017

This failure was unrelated - going to rebase and then try to merge this.

@gaearon
Copy link
Collaborator

gaearon commented Jun 12, 2017

We decided against this, as it's easy to test 15 build products from master fixtures, and maintaining fixtures in both places doesn't seem worth the effort.

@gaearon gaearon closed this Jun 12, 2017
@flarnie flarnie deleted the addDomFixtureTo15.6-dev branch May 25, 2018 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants