1

Foreword, I'm fairly new to using git and versioning systems in general. I think I understand most of the concepts, but i seem to have run into a wall here/ I'm using smartgit as my client, which may be relevant, and coding for a game server

So a couple of weeks ago, I started on a major project, branching off of our project's development branch. During that time, there's been a major update to the codebase, and a few things have changed that cause my branch to not compile. Apparently, it's not using the current development branch as a base, but the state of the development branch when I started this project, and the new changes don't seem to be merging into the local code

I've just started using smartgit, and there's a whole tide of features I don't quite understand.

Here's the tooltip branch for my project, DionaOverhaul: enter image description here

The base branch that I originally branched off of, was aurorastation/development. I'm thinking maybe that should be set as the tracked branch?

I need to merge all the changes to aurorastation/development into my dionaoverhaul branch somehow, and create a branch that has all the current development code, with my dionaoverhaul commits ontop of it. and I'm not sure how to go about it.

After a bit of research, i think what i want to do is to rebase my branch to the tip of aurorastation/development

but one problem i see with that, is that at least one of the tiles i'm working on, has been changed in the meantime, and i don't want to entirely overwrite the changes to that file, with the version that's in my branch. I'm not sure if that's something the repository manager will handle when merging my pull request, or whether its something i need to take care of during the rebase

Nanako
  • 59
  • 7

2 Answers2

0

You have two branches: your_local and development.

Once you finished your_local and want to bring all the changes to development you have two options:

  1. Switch back to development branch, pull all the changes in, and merge your_local into it.
  2. Switch back to development, pull all the changes in, switch back you your_local, merge development into it and resolve all the conflicts. Then go to option 1.

First option is a simple case when you have no big changes in development.

The second one looks like your case: there are changes in development and they are conflicting with yours.

Actually, there are more (you can rebase your_local onto latest development for example), but let's keep is simple for now.

Tracking branch

You don't need to change tracked branch, this is a pointer to the remote copy of your local branch.

Conflicts

when you have conflicting changes in both development and your_local git will try to resolve it (that's what git is for). However it's not always possible and git will mark such files as conflicting, and you will have to manually resolve those conflicts.

Smartgit has some basic functionality for merging and resolving conflicts.

Anyway, if you're not very familiar with git/smartgit I recommend you to backup your repository so that you can experiment with merge without worrying too much.

Community
  • 1
  • 1
Anton Sizikov
  • 9,105
  • 1
  • 28
  • 39
0

Tracked Branch

"Tracked branch" means the branch that you push to. It should always be the same as the name of the local branch, prefixed by "refs/remotes/NAME_OF_REMOTE". NAME_OF_REMOTE can be anything, but if you only push to one server, the convention is to call it "origin". So don't change it. If you do, the next time you push, you will get a message that you can't push because it would overwrite the remote branch, and if you're sure you want to do that, use git push --force. If you use git push --force, you will end up overwriting someone else's hard work on the development branch. (Yes, it is recoverable, but it's a headache so just don't.)

Merging Changes

I need to merge all the changes to aurorastation/development into my dionaoverhaul branch somehow, and create a branch that has all the current development code, with my dionaoverhaul commits ontop of it

You have 2 options. If you really want all your dionaoverhaul commits ontop of it, then do this:

  1. git fetch # This downloads all the latest changes from the server
  2. Make sure you are on the dionaoverhaul branch.
  3. git rebase origin/development The terminal will show you that it's applying the commits on your branch, one at a time. Periodically, it will stop and tell you there are conflicts that need to be resolved manually. You may have to do this several times. Each time, resolve the conflicts in each file, and then git add -A && git rebase --continue

On the other hand, if you'd prefer to only have to deal with at most 1 set of manual conflicts, then use merge instead of rebase. The disadvantage is that your branch's history will no longer be one straight line. There are many advantages to this approach, however, that are byond the scope here. To merge, instead of running git rebase origin/development, run git merge origin/development. Again, you may have to deal with manual conflicts, but once they are all resolved, use git add -A && git commit.

Isaac Betesh
  • 2,935
  • 28
  • 37
  • Thanks everyone, rebasing is what i went with eventually, with the help of several tutorials. i combed through the conflicts with smartgit and fixed them. Learned a lot in this process – Nanako Jun 28 '16 at 15:42