Managing repository size
Currently, we are storing preview images and benchmark screenshots directly within the main repository. This approach has a significant drawback: as we add more versions and assets, the repository size will grow rapidly.
To keep the repository lean:
- Move assets: Create a separate public repository specifically for storing these images.
- Link externally: Reference the images in our main documentation or posts using their public URLs instead of local file paths.
This will help keep our primary codebase lightweight and easier to manage.
Managing repository size
Currently, we are storing preview images and benchmark screenshots directly within the main repository. This approach has a significant drawback: as we add more versions and assets, the repository size will grow rapidly.
To keep the repository lean:
This will help keep our primary codebase lightweight and easier to manage.