CiviCRM Community Forums (archive)

That all looks right to me.
Looks like you're missing the last step (pushing your changes back to github)
>git push origin CRM-13789

I'm not sure what you mean you deleted kenwest/civicrm-core.

The basic idea with a PR is to create a branch based off the latest upstream (civicrm on github), and then push it to origin (your fork on github). Once you do that, you can go to github.com and create a PR from your branch to the appropriate civicrm branch (in this case 4.4). To me it looks like you did everything right but got confused with the last step. The reason you see stray commits from lobo is because you were comparing your branch with master instead of 4.4.

This is the comparison you want: https://github.com/kenwest/civicrm-core/compare/4.4...CRM-13789-1

Those instructions assume the fork exists on github. So you can skip that step.
The interesting thing to note is that the state of a personal fork doesn't matter very much.
For example, say your fork on github has the following branches:

master - this will be an out-of-date copy of civicrm/master. No one cares what's in it. Delete it if you wish.
4.4 - an out-of-date copy of civicrm/4.4. No one cares what's in it. Delete it if you wish.
some-old-issue - a branch you used to send a PR to civicrm a while ago. If the PR has been merged the branch no longer matters. Delete it.
some-current-issue - a branch for an active PR. This is the only branch that matters. You can push more commits to it to update the PR. When the PR is closed, delete it.

So now that you have your mostly placeholder fork on github, here's how to use it to send a PR against, for example, 4.4:

>git checkout 4.4 (assuming you have this local branch already. If it doesn't exist yet type 'git checkout upstream/4.4 -b 4.4')
>git pull upstream 4.4
check how you're doing with
>git status
If the pull fails or your git status is not clean do
>git reset --hard HEAD
and try pulling again
now you have an up-to-date copy of civicrm 4.4. You can play with it and try to reproduce the issue you're wanting to fix
whenever you get out-of-date, 'git pull upstream 4.4' again.
If you've made some code changes and want to send a PR, do:
>git checkout -b some-branch-name
>git commit -a -m "CRM-xxx - Added foo bar to whiz bang"
>git push origin some-branch-name
You can now create a PR on github.
If you have more changes to make and want to add them to the PR, do the commit and push again
If you get out-of-date and it really matters (usually being behind by a few commits on a PR branch doesn't matter, but if the upstream changes are something you really need):
>git pull --rebase upstream 4.4
>git push --force origin some-branch-name
when your PR has been merged, delete your branch
>git checkout 4.4
>git branch -d some-branch-name
>git push origin :some-branch-name
Now you can pull to get the latest 4.4 and you're back to work

Note that this doesn't have to be a linear process. If you have more than one PR you are working on at once, you can switch back and forth between branches freely. Just remember that when you first create a branch for a PR, you should always start on the (up-to-date) branch that this PR is for. So note in the example above we were on 4.4 before creating some-branch-name.

Also note that in git there are hundreds of ways to do the same thing and it's largely a matter of personal preference. What I gave you was my own worflow, which works for me. The instructions on the wiki are slightly different but will achieve the same result. For example if you want to skip the step of updating 4.4 locally before creating a PR branch, you can just create the branch directly from upstream
>git checkout upstream/4.4 -b some-branch-name