Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Git folder is large

Open
#295 4 comments 0 reactions 1 assignee View on GitHub

@DCMattyG is already working on this.

Since Jul 8, 2024.

Assessment

This issue has not been assessed yet.

Description

Describe the bug

The repo is growing rapidly(!) Caused by every version of the 50mb asset zip file is beeing kept in the git history.

Could this zip file instead be generated on-demand from inside the deploy.ps1 script?
Should the repo be cleaned up with git filter-branch or something similar to remove the large .pack file and lower the repo size?

Git clone fetches over 500mb
PS C:\git> git clone https://github.com/Azure/ipam
Cloning into 'ipam'...
remote: Enumerating objects: 5577, done.
remote: Counting objects: 100% (2470/2470), done.
remote: Compressing objects: 100% (788/788), done.
remote: Total 5577 (delta 1688), reused 2318 (delta 1577), pack-reused 3107
Receiving objects: 100% (5577/5577), 503.54 MiB | 10.88 MiB/s, done.
Resolving deltas: 100% (3443/3443), done.
PS C:\git>
Largest 5 files in the repo
PS C:\git\ipam> Get-ChildItem -File -Recurse -Force | Sort-Object Length -Descending | Select-Object -First 5 -Property Directory, Name, @{l="Size in MB" ; e={"{0:N2}" -f ($_.Length / 1mb)}}

Directory                     Name                                               Size in MB
---------                     ----                                               ----------
C:\git\ipam\.git\objects\pack pack-f54811749458d296170445b28f83394b70b19e89.pack 503.54
C:\git\ipam\assets            ipam.zip                                           52.83
C:\git\ipam\docs\images       ipam-logo.png                                      0.49
C:\git\ipam\ui                package-lock.json                                  0.43
C:\git\ipam\docs\api\images   postman_response.png                               0.25
Dominant language
JavaScript
Stars
326
Forks
111
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/ipam

All issues in Azure/ipam

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.