ScopeLimitEntry
A per-resource limit: the maximum in force and what it applies to. Usage is reported on each
resource, so there is no used here.
Shape
- limitinteger · int640–∞
- nameLimitNamestorage_bytesconcurrent_pipeline_runspipeline_runs_this_monthpipeline_minutes_this_monthreposmembersteamscustom_rolesaccess_limitsapproval_rulesscim_tokenswebhooksservice_accountsbranch_rulesprovider_connectionsprovider_installsopen_issueslabelsmilestonesblueprintswiki_pagesservicesenvironmentsscorecardspipeline_componentsopen_mrs_per_repocomments_per_mrbranches_per_repotags_per_reporeviewers_per_mrreleases_per_repopipelines_per_repoanchors_per_repocriteria_per_repocode_todos_per_reporeactions_per_commentcommit_statuses_per_commitcomments_per_issuerelations_per_issuechildren_per_issueanchors_per_issuecriteria_per_issuesso_invites_per_scopepush_bytespackage_bytesrelease_asset_bytespipeline_dag_nodesversions_per_pipeline_componentmembers_per_teamWhich limit a usage-and-limits entry describes.
- scopeLimitScoperepomerge_requestissuecommentcommitreleasepushrunpackagepipeline_componentteamnamespaceWhat a per-resource limit applies to — each repository, each merge request, each team, and so on. Usage against it is reported on that resource, not in the organization-wide view.
Example
Synthesized example{
"limit": 89,
"name": "storage_bytes",
"scope": "repo"
}
Graph
Used inside
Contains
No named schema inside.
Used by
Sent by 0 operations
No operation takes it as a request body.
Returned by 0 operations
No operation returns it directly.