Previously I had my own git-clone of the svn-repository and there are some differences that make me wonder how you keep git and svn in sync.

1) with git svn clone I get a reference to the svn commit (like git-svn-id: ... trunk@3568 ...) this Info is not present in github.
Maybe not needed that badly, but otherwise it does not hurt to have it there ... so I wonder why it was removed.

2) you make some effort to place the version tags outside the master branch. why? This way `git describe` does not provide usefull information.
I think "1.1.10-3-g032224e" (3 commits after 1.1.10 release) would be much more usefull than "heads/master".

Its great to see yii community exploring github. Now since it is very easy to provide a fix with pull requests Yii can grow much faster I think.
I am amazed, how many pull requests, forks and watches we have within one day. With github you get a feeling about whats going on in the community

At the moment of I am writing this post we have 23 pull requests, 318 watchers and 51 forks!

CeBe: Since you seem to be proficient with git/github: I'm currently creating a branch for every patch I'd like to submit via a pull request. Is that the right way to do? I fear to taint my pull requests with unrelated commits

programmer /ˈprəʊgramə/, noun: a device that converts ►coffee into ►code

CeBe: Since you seem to be proficient with git/github: I'm currently creating a branch for every patch I'd like to submit via a pull request. Is that the right way to do? I fear to taint my pull requests with unrelated commits

Yes it is definitively the right way, you should not commit anything to master since you would not be able to get new changes from upstream repository without creating unneccessary merge commits and spoil the history.
I also noticed that you did something like rebasing with your master branch, so there are commits authored by other people and committed by you. You should not use your master branch for creating branches for pull requests anymore.
Since github does not allow you to change history, I am afraid there is no way to fix this.

Da:Sourcerer, on 17 February 2012 - 04:35 PM, said:

[...]After all, we've already got two bugtrackers now.

Google code bugtracker is deprecated, we only have github as the bugtracker now.

I also noticed that you did something like rebasing with your master branch, so there are commits authored by other people and committed by you. You should not use your master branch for creating branches for pull requests anymore.
Since github does not allow you to change history, I am afraid there is no way to fix this.

What? I was trying to keep my fork in sync with upstream, that's all

Well, fits quite well with the rest: Something must have broken so fundamentaly that I am no longer able to push to my very own branches.

programmer /ˈprəʊgramə/, noun: a device that converts ►coffee into ►code

You should pull upstream before every push to github. As long as there are no merge conflicts before you open or update your pull request, you've done your job. If a long time passes because of discussion a member of the Yii team should attempt to resolve the merge conflicts themselves, if the merge is particularly tricky they will ask for your help. Of course you can be proactive about this and if you notice conflicts while a pull request is open, you can make the Yii team's life easier by resolving them yourself.

Seen that. Unfortunately I can no longer follow this as my local git gave up on me. I can commit changes, but that will kick me out of my branch. Anyway, I think I hit my "damn you git!"-quota for this week. I'll check back with this next wednesday.