-
Notifications
You must be signed in to change notification settings - Fork 1
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
merge conflict #22
Comments
Changes to be committed:
Unmerged paths:
this is what my terminal says |
@laurenmcguigan are you on campus? |
@laurenmcguigan I am in the faculty lounge if you want to come here. |
Im not on campus and I won't be there until tomorrow. On my desktop I have the changes I made and the ones you made but it's appearing with a bunch of <<<<<<<<<<<<<HEAD I don't know what that means. |
@laurenmcguigan yea those get inserted whenever the files have diverged they indicate where the files are different. The changes you made are they just to the end of the document? |
@laurenmcguigan like after the point where my comment indicates where we left off? |
Its just at the bottom. I added more occupants. |
@laurenmcguigan if you were just adding onto the file then there should be no issue merging our two files together. If you do git status, then git add -A, then git commit -m "with your message in here" then git status again it should say that you and the remote have diverged... at that point if you do git pull the window should pop up for you to merge the commit ... let me know if it does and I will tell you where from there... |
when the pop-up box comes up use this issue to save the merge commit message and get back to terminal then at that point you should be able to commit one more time (basically adding and committing the newly merged file) and then push without an issue. |
So it seems like it is fixed and everything is there. I just still have those weird head things that are making oxygen angry. can I just delete them? |
ehhh if they are there that means one of our changes is likely not showing up. Dr. B had gone in and made some edits as well soooo I am not sure if you would recognize if all the changes are there or not. I guess just go in and delete those head things for now and finish your markup and push then we can see if everything merged correctly tomorrow when we get together. |
I think it is fixed |
@laurenmcguigan It looks fine to me--but this is a little brittle to check without a schema! |
@RJP43 I made changes to the graveyard info file before I could pull yours in and now I have a merge conflict. How do I fix it?
The text was updated successfully, but these errors were encountered: