Closed ESmith92 closed 8 years ago
you have some merge conflicts that you'll need to resolve before we can merge this in
@ESmith92 To resolve merge conflict, do the following:
git checkout develop
to check out your local develop
branch.git pull origin develop
to pull latest develop
branch from GitHub.git checkout EricS-GeoCoder
to check out your branch.git merge develop
to merge develop
into your EricS-GeoCoder
branch. Oh no! Merge conflict! No worries.git status
, you'll see a bunch of files in green, followed by this:
deleted by us: src/providers/reverse-geocoder-class.php
deleted by us: test/spec/SearchApi/Providers/ReverseGeocoderClassSpec.php
git rm <FULL FILE PATH HERE>
. So git rm src/providers/reverse-geocoder-class.php
for the first file. Do the same with the second. You need to do this since develop
has these files, but in your branch they have been deleted. When the merge occurred, git isn't sure whether these files should still exist or not, hence the merge conflict. git rm ...
will tell git that you'd like these files deleted.git commit
, use the same git commit message when prompted. A merge is basically a giant commit that takes the changes you don't have and apply them as one big commit. When a merge conflict had occurred, the commit was suspended. That's why you'd need to do another git commit
. A git commit
without a message will put git in some interactive mode that asks for the message. If you have followed these steps correctly, you should see something like Merge X to Y
as the commit message.git push origin EricS-GeoCoder
and cross your fingers.
refactor reverse geocoder and related classes
-refactor GoogleReverseGeocoder and spec -GoogleReverseGeocoderParser and spec -GoogleURLBuilder and spec