-
Notifications
You must be signed in to change notification settings - Fork 81
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
Branching and Merging- Not without Conflicts! #75
Labels
everyone
For competitive issues, best PRs are only merged, no need to assign yourself
open-for-all
Any one can work on it without getting assigned, every PR can merge
Points: 20
Comments
Merged
Merged
Closed
Merged
Merged
Merged
Merged
Note that the file should contain the flop as well as the hit films after resolution of the conflict. |
Merged
Closed
Merged
Merged
Merged
Closed
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Closed
Merged
Merged
Merged
Merged
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
everyone
For competitive issues, best PRs are only merged, no need to assign yourself
open-for-all
Any one can work on it without getting assigned, every PR can merge
Points: 20
Steps to solve this task:
The Pull Request must contain 3 screenshots, 1 for the initial 3 commits, 1 showing the merge conflict, and the 3rd one showing the commit where the merge conflict has been resolved.
This issue is open for all, so no need to claim it. Just submit your PR.
Note that the file should contain the flop as well as the hit films after resolution of the conflict.
The text was updated successfully, but these errors were encountered: