Obtaining Repository Statistics Summary
Function
This API is used to obtain repository statistics summary.
Debugging
You can debug this API through automatic authentication in API Explorer or use the SDK sample code generated by API Explorer.
URI
GET https://{hostURL}/v4/repositories/{repository_id}/statistics-summary
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| repository_id | Yes | Integer | Definition You can query the project list to obtain the repository ID by calling the API used to query user's all repositories. Constraints N/A. Value range: 1~2147483647 |
Request Parameters
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| X-Auth-Token | Yes | String | Definition User token. Obtain a token by calling the IAM API for obtaining a user token. The value of X-Subject-Token in the response header is the user token. Constraints Mandatory. Range 1–100,000 characters. Default Value N/A. |
Response Parameters
Status code: 200
| Parameter | Type | Description |
|---|---|---|
| branches_count | Integer | Definition: Number of branches. Value range: N/A. Value range: 1~2147483647 |
| commits_count | Integer | Definition: Commits. Value range: N/A. Value range: 1~2147483647 |
| members_count | Integer | Definition: Number of members. Value range: 1~2147483647 |
| tags_count | Integer | Definition: Number of tags. Value range: N/A. Value range: 1~2147483647 |
| merge_request_count | Long | Definition: Number of merge requests. Value range: N/A. Value range: 1~2147483647 |
| note_count | Long | Definition: Number of remarks. Value range: N/A. Value range: 1~2147483647 |
Example Requests
None
Example Responses
Status code: 200
Obtain the latest push event of a repository.
{
"branches_count" : 2,
"commits_count" : 8,
"members_count" : 8,
"tags_count" : 0,
"merge_request_count" : 0,
"note_count" : 0
} Status Codes
| Status Code | Description |
|---|---|
| 200 | Obtain the latest push event of a repository. |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.