Lists public repositories for the specified user. Note: For GitHub AE, this endpoint will list internal repositories for the specified user.
Can be one of all, owner, member.
Allowed values:allownermember
Default:owner
Can be one of created, updated, pushed, full_name.
Allowed values:createdupdatedpushedfull_name
Default:full_name
Can be one of asc or desc. Default: asc when using full_name, otherwise desc
Allowed values:ascdesc
Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
Response
Minimal Repository
Example:1296269
Example:MDEwOlJlcG9zaXRvcnkxMjk2MjY5
Example:Hello-World
Example:octocat/Hello-World
Simple User
Example:https://github.com/octocat/Hello-World
Example:This your first repo!
Example:https://api.github.com/repos/octocat/Hello-World
Example:http://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}
Example:http://api.github.com/repos/octocat/Hello-World/assignees{/user}
Example:http://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/branches{/branch}
Example:http://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}
Example:http://api.github.com/repos/octocat/Hello-World/comments{/number}
Example:http://api.github.com/repos/octocat/Hello-World/commits{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}
Example:http://api.github.com/repos/octocat/Hello-World/contents/{+path}
Example:http://api.github.com/repos/octocat/Hello-World/contributors
Example:http://api.github.com/repos/octocat/Hello-World/deployments
Example:http://api.github.com/repos/octocat/Hello-World/downloads
Example:http://api.github.com/repos/octocat/Hello-World/events
Example:http://api.github.com/repos/octocat/Hello-World/forks
Example:http://api.github.com/repos/octocat/Hello-World/git/commits{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/git/refs{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/git/tags{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/issues/comments{/number}
Example:http://api.github.com/repos/octocat/Hello-World/issues/events{/number}
Example:http://api.github.com/repos/octocat/Hello-World/issues{/number}
Example:http://api.github.com/repos/octocat/Hello-World/keys{/key_id}
Example:http://api.github.com/repos/octocat/Hello-World/labels{/name}
Example:http://api.github.com/repos/octocat/Hello-World/languages
Example:http://api.github.com/repos/octocat/Hello-World/merges
Example:http://api.github.com/repos/octocat/Hello-World/milestones{/number}
Example:http://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}
Example:http://api.github.com/repos/octocat/Hello-World/pulls{/number}
Example:http://api.github.com/repos/octocat/Hello-World/releases{/id}
Example:http://api.github.com/repos/octocat/Hello-World/stargazers
Example:http://api.github.com/repos/octocat/Hello-World/statuses/{sha}
Example:http://api.github.com/repos/octocat/Hello-World/subscribers
Example:http://api.github.com/repos/octocat/Hello-World/subscription
Example:http://api.github.com/repos/octocat/Hello-World/tags
Example:http://api.github.com/repos/octocat/Hello-World/teams
Example:http://api.github.com/repos/octocat/Hello-World/git/trees{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/hooks
Example:2011-01-26T19:06:43Z
Example:2011-01-26T19:01:12Z
Example:2011-01-26T19:14:43Z
A git repository
Code Of Conduct
Example:0
Example:0
Example:0
Look for stuff on GitHub.
Searches for query terms inside of a file. This method returns up to 100 results per page.
When searching for code, you can get text match metadata for the file content and file path fields when you pass the text-match media type. For more details about how to receive highlighted search results, see Text match metadata.
For example, if you want to find the definition of the addClass function inside jQuery repository, your query would look something like this:
q=addClass+in:file+language:js+repo:jquery/jquery
This query searches for the keyword addClass within a file’s contents. The query limits the search to files where the language is JavaScript in the jquery/jquery repository.
Due to the complexity of searching code, there are a few restrictions on how searches are performed:
master branch.language:go is not valid, while amazing language:go is.The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See “Searching code” for a detailed list of qualifiers.
Sorts the results of your query. Can only be indexed, which indicates how recently a file has been indexed by the GitHub Enterprise Server search infrastructure. Default: best match
Allowed values:indexed
Determines whether the first search result returned is the highest number of matches (desc) or lowest number of matches (asc). This parameter is ignored unless you provide sort.
Allowed values:descasc
Default:desc
Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
Response
Code Search Result Item
Find commits via various criteria on the default branch (usually master). This method returns up to 100 results per page.
When searching for commits, you can get text match metadata for the message field when you provide the text-match media type. For more details about how to receive highlighted search results, see Text match
metadata.
For example, if you want to find commits related to CSS in the octocat/Spoon-Knife repository. Your query would look something like this:
q=repo:octocat/Spoon-Knife+css
The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See “Searching commits” for a detailed list of qualifiers.
Sorts the results of your query by author-date or committer-date. Default: best match
Allowed values:author-datecommitter-date
Determines whether the first search result returned is the highest number of matches (desc) or lowest number of matches (asc). This parameter is ignored unless you provide sort.
Allowed values:descasc
Default:desc
Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
Response
Commit Search Result Item
Find issues by state and keyword. This method returns up to 100 results per page.
When searching for issues, you can get text match metadata for the issue title, issue body, and issue comment body fields when you pass the text-match media type. For more details about how to receive highlighted
search results, see Text match metadata.
For example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.
q=windows+label:bug+language:python+state:open&sort=created&order=asc
This query searches for the keyword windows, within any open issue that is labeled as bug. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.
Note: For user-to-server GitHub App requests, you can’t retrieve a combination of issues and pull requests in a single query. Requests that don’t include the is:issue or is:pull-request qualifier will receive an HTTP 422 Unprocessable Entity response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the is qualifier, see “Searching only issues or pull requests.”
The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See “Searching issues and pull requests” for a detailed list of qualifiers.
Sorts the results of your query by the number of comments, reactions, reactions-+1, reactions--1, reactions-smile, reactions-thinking_face, reactions-heart, reactions-tada, or interactions. You can also sort results by how recently the items were created or updated, Default: best match
Allowed values:commentsreactionsreactions-+1reactions--1reactions-smilereactions-thinking_facereactions-heartreactions-tadainteractionscreatedupdated
Determines whether the first search result returned is the highest number of matches (desc) or lowest number of matches (asc). This parameter is ignored unless you provide sort.
Allowed values:descasc
Default:desc
Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
Response
Issue Search Result Item