Search Issue Tracker
By Design
Votes
0
Found in
3.17.2
Issue ID
UUM-140269
Regression
No
Remote repository size is not shown for GitHub repositories when expanding project details
Steps to reproduce:
- Open Unity Hub
- Click "+ New project"
- In the "Source control provider" select "GitHub"
- Make sure "Create and push initial commit is checked"
- Create the project
- Once created, in the Projects tab expand the created project
- Observe the value next to "Remote repository size"
Actual results: No value is shown next to "Remote repository size"
Expected results: The remote repository size is shown for the created GitHub repository
Reproducible with versions: 3.17.2
Tested on (OS): Ubuntu 24.04, macOS 26.4
Notes:
- Size is shown correctly for GitLab and UVC
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some post-processing volume overrides only update after a refresh when using HDRP
- Video Player glitches when Skip On Drop is enabled
- GameObject movement in Scene view becomes stuttery and intermittently freezes when using non-standard pointers across editor tabs or window boundaries
- Addressables.CheckForCatalogUpdates() always returns 0 when "Only update catalogs manually" is enabled
- VFX Graph forces a lengthy recompilation freeze when exiting Play Mode with a cloned Render Pipeline asset
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
The repo is initially created empty, and then GitHub has a delay in reporting the size after the initial commit. A temporary empty value '-' is expected, and the actual value should be populated after a small delay in time.
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
The repo is initially created empty, and then GitHub has a delay in reporting the size after the initial commit. A temporary empty value '-' is expected, and the actual value should be populated after a small delay in time.