Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings
This repository was archived by the owner on Nov 1, 2017. It is now read-only.

Swap :user for :owner for clarity#150

Merged
pengwynn merged 1 commit intomasterfromclearer-owner-repo
Sep 24, 2012
Merged

Conversation

@pengwynn
Copy link
Contributor

I've seen a number of new API users get tripped up on the :user
parameter when they're looking up a repository that belongs to an org.
This changes all the :user/:repo pairs in the docs to :owner/:repo to be
a bit clearer.

I've seen a number of new API users get tripped up on the :userparameter when they're looking up a repository that belongs to an org.This changes all the :user/:repo pairs in the docs to :owner/:repo to bea bit clearer.
@pengwynn
Copy link
ContributorAuthor

/cc @github/api

@technoweenie
Copy link
Contributor

Ah thank god, I've wanted to do this forever :)

@sigmavirus24
Copy link
Contributor

👍

@paul
Copy link
Contributor

Awesome.:shipit:

Related, but I'd also like to change the response documents the same way. We say:user a lot, when we mean something more specific, like:owner or:author or:committer. Not sure how to go about doing it without breaking everybody's shit, though. We'd have to either 1) Go ahead and add the other field(s) and leave :user, and just deal with it being ambiguous or 2) Bump the revision :(

@pengwynnpengwynn merged commita5414d2 intomasterSep 24, 2012
@technoweenie
Copy link
Contributor

Related, but I'd also like to change the response documents the same way.
We say :user a lot, when we mean something more specific, like :owner or
:author or :committer. Not sure how to go about doing it without breaking
everybody's shit, though. We'd have to either 1) Go ahead and add the other
field(s) and leave :user, and just deal with it being ambiguous or 2) Bump
the revision :(

@paul: We can work that into the upcoming "real" v3. Essentially, I'd add
the extra fields now, and then remove the old ones in the next version. I
have a laundry list of changes for the next revision bump. You can start
documenting the ones you want to change in the 'Expected Changes' area:
http://developer.github.com/

izuzak added a commit that referenced this pull requestNov 24, 2014
Document hook delivery headers and payload attributes
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@pengwynn@technoweenie@sigmavirus24@paul

[8]ページ先頭

©2009-2025 Movatter.jp