CODEWITHSUNDEEP
gitgithub
David West
David West

Reputation: 1590

GitHub Merge Conflicts

Newbie Alert! .............. Hi guys, I was rather silly yesterday and downloaded my project from Github and then proceeded to edit that new project locally, as I deemed that easier than resolving conflicts with my previous local project.

I went to push last night and it asked me to pull, as it was effectively seeing a new Git repository, with no history. I then went to pull, as requested, and it killed my app and only partly pulled from Github. It was saying there were merge conflicts to resolve, so to ensure I didn't lose my work...I opted to do a hard reset and hey presto... the app works again locally as before. Thank goodness.

How would I go about either:

Upvotes: 0

Views: 143

Answers (1)

MarkyMark
MarkyMark

Reputation: 53

Here's what we currently do.

1. From a clean machine, clone project from GitHub using "git clone https://github.com/path_to_project.git".
2. Make local changes and do a "git add file_name" for each updated file/object.
3. After "git add", we do a "git commit -m "commit_message_here"".
4. After "git commit", we first do a "git fetch origin" to get updates from other people working on our project.
5. After "git fetch", we do a "git merge origin/master" to merge updates into our local copies.
6. In case of "conflicts", we do it manually. Files with conflicts will be marked and prefixed/suffixed with some strings.
7. After resolving our conflicts, we again do "git add" for those resolved files... then "git commit" again.
8. Finally, it is safe to do "git push origin master".

I recommend to use "fetch+merge" vs. "pull". I can't find the reference from a forum I read that details why it is better.

Upvotes: 1

Related Questions