Yeah, I'll go with what Will wants and change these per his suggestions.

> On Jun 15, 2013, at 15:30, Konrad Malawski <notifications@github.com> wrote:
> 
> In github/events.go:
> 
> > +	return payload
> > +}
> > +
> > +// PushEvent represents a git push to a GitHub repository.
> > +//
> > +// GitHub API docs: http://developer.github.com/v3/activity/events/types/#pushevent
> > +type PushEvent struct {
> > +	PushID  int          `json:"push_id,omitempty"`
> > +	Head    string       `json:"head,omitempty"`
> > +	Ref     string       `json:"ref,omitempty"`
> > +	Size    int          `json:"ref,omitempty"`
> > +	Commits []PushCommit `json:"commits,omitempty"`
> > +}
> > +
> > +// PushCommit represents a git commit in a GitHub PushEvent.
> > +type PushCommit struct {
> This question will come up in all APIs I think - (it's the same with Tree and many more I believe), it comes down to the question discussed elsewhere "one type with nulls vs. many specific types". I think @willnorris foted for the one-type approach + good docs... I'd personally like the "many types" one, but we'd best agree on some 
> naming scheme for those then hm...
> 
> Just sayin' because I'll PullReq a few things soon (Trees pretty much ready for example), and I'm wondering which style to use.
> 
> —
> Reply to this email directly or view it on GitHub.