Skip to content
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

Open
shauryaaa100 opened this issue Dec 18, 2024 · 1 comment
Open

Branching and Merging- Not without Conflicts! #75

shauryaaa100 opened this issue Dec 18, 2024 · 1 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

Comments

@shauryaaa100
Copy link
Collaborator

shauryaaa100 commented Dec 18, 2024

Steps to solve this task:

  • Create a folder named 'Task-2'. The name should be exactly same as this. If it already exists, no need to create it.
  • In the Task-2 folder, add a .txt file named after your github username. Example- shauryaaa100.txt
  • In that file, write your favorite actor's name in line 1. Commit this change.
  • Create a new branch called 'Task2', and checkout to that branch.
  • In the file you had created, add 2 hit films of the actor in lines 2 and 3. Commit this change.
  • Checkout to main branch, and add 2 flop films of the actor in lines 2 and 3. Commit this change.
  • Take a screenshot of the previous 3 commits. You can use git log or git log --oneline.
  • Now, merge the 'Task2' branch into the main branch.
  • There will be a merge conflict. Take a screenshot of this merge conflict.
  • Resolve the merge conflict. Take a screenshot of the commit resolving the merge conflict.
  • Push the changes and create a Pull Request.

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.

@shauryaaa100 shauryaaa100 added Points: 20 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 labels Dec 18, 2024
This was referenced Dec 18, 2024
@23abdul23 23abdul23 mentioned this issue Dec 19, 2024
@shauryaaa100
Copy link
Collaborator Author

Note that the file should contain the flop as well as the hit films after resolution of the conflict.

shauryaaa100 added a commit that referenced this issue Dec 19, 2024
@shrut2606 shrut2606 mentioned this issue Dec 19, 2024
@Atharwa23 Atharwa23 mentioned this issue Dec 19, 2024
@Abhilash-0322 Abhilash-0322 mentioned this issue Dec 19, 2024
@iking07 iking07 mentioned this issue Dec 19, 2024
@saurabhk9919 saurabhk9919 mentioned this issue Dec 19, 2024
@23abdul23 23abdul23 mentioned this issue Dec 19, 2024
@nubEA nubEA mentioned this issue Dec 19, 2024
shauryaaa100 added a commit that referenced this issue Dec 20, 2024
This was referenced Dec 20, 2024
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
Projects
None yet
Development

No branches or pull requests

1 participant