-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add tip on solving merge conflicts in functional tests #2261
Add tip on solving merge conflicts in functional tests #2261
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work @yucheng11122017! LGTM besides the small nit! Useful tip that I think many future developers will find useful!
3. Checkout to PR branch | ||
4. Merge local master into PR branch | ||
- `git merge master` | ||
5. Accept any change to conflicts in generated test files |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps we could include examples of files/filetypes of generated functional test files!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @itsyme, thanks for the comment! I added a tooltip explaining the location of these expected files above (expected
for functional and __snapshot__
for unit test)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Just some nits on the wording 👍
Thanks for the review @lhw-1! Fixed the nits and responded to your comments :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for fixing the nits! Unfortunately, I have more nits (sorry) 😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
What is the purpose of this pull request?
Overview of changes:
Add tip on solving merge conflict in functional test expected results
Tip based on comment by @tlylt
Anything you'd like to highlight/discuss:
Testing instructions:
Proposed commit message: (wrap lines at 72 characters)
Add tip on solving merge conflicts in functional tests
Checklist: ☑️