Limits
Every limit here reports itself rather than failing silently. These are the numbers to plan around.
#Every limit
Limit | Value | What happens |
|---|---|---|
Branches | First 100 only | Only the first 100 branches in a repository are fetched. Any beyond that do not appear. |
Folder contents | - | A folder is listed in one go, so a very large folder may show incompletely. |
Repository list | 100 per page | Your repositories load 100 at a time. |
Public repository search | First page only | Search runs only when you type a query and you are on the first page of results. Paging past the first page shows only your own repositories. |
Auto-convert of pasted links | Up to 10 path levels after the branch | Files nested deeper than 10 levels after the branch name do not convert automatically. |
Image height | 800px | Images display at 800px tall at most. |
Code viewer height | 600px | The code viewer is 600px tall at most. |
Long Markdown files | - | Very long Markdown files are displayed in a different way. |
Connecting a GitHub account | 30 seconds | Capable stops waiting for the connection to finish after 30 seconds. |
GitHub rate limits | Not handled | Capable does not retry when GitHub rate limits a request. A GitHub 403 caused by rate limiting is reported as an access error, as though nobody has access. |
Large files | - | Large files can be slow to load, or fail. |
#A few things worth knowing
A limit that is reached is reported in the interface, not in a log you have to find.
Limits are per site or per tenant depending on the limit. The table says which.
Edition can change some of these.
#Related
They announce themselves. Read the message.
