You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If the repository contains too many branches, the first loading of commits tab takes too long. This is particularly visible if the number of branches is greater than 100, since that would mean waiting for another GraphQL request.
Additional context
This was known during the development times itself, and had no other option. There is no API from github that lists commits across all branches sorted by commit date. Either that, or an API that lists branches sorted by head commit date could solve this problem. AFAIK, neither exists and a fresh solution would be required.
The text was updated successfully, but these errors were encountered:
Describe the bug
If the repository contains too many branches, the first loading of commits tab takes too long. This is particularly visible if the number of branches is greater than 100, since that would mean waiting for another GraphQL request.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The loading should be way faster than this.
Screenshots
NA
Version information:
Additional context
This was known during the development times itself, and had no other option. There is no API from github that lists commits across all branches sorted by commit date. Either that, or an API that lists branches sorted by head commit date could solve this problem. AFAIK, neither exists and a fresh solution would be required.
The text was updated successfully, but these errors were encountered: