Issue pushing large dashboard files or folders to GitHub after Git integration

[Pravin_Suwasiya]

I have integrated my Microsoft Fabric environment with GitHub, and my Fabric workspace is successfully synced with the main branch. For each dashboard, Fabric creates two folders in the repository: one for the semantic model and one for the report. When I pull the repository from GitHub, all dashboards are pulled correctly using this folder structure. I am able to make changes to the existing repository and push those changes back to the remote branch.

However, I am facing an issue when the folder or file size increases (around 50–100 MB or more). In such cases, the push to the remote GitHub branch fails with an error related to large files or authentication. I have tried logging in both with a user account and with a personal access token, but the issue persists. I would like to understand how to handle large Fabric report or semantic model files in GitHub and what the recommended solution is to avoid this push failure.

[v-dineshya]

Hi @Pravin_Suwasiya ,

Thank you for reaching out to the Microsoft Community Forum.

Hi @cengizhanarslan , @svenchio  and @Thomaslleblanc  , Thank you for your prompt responses.

Hi @Pravin_Suwasiya , Could you please try the proposed solutions shared by @cengizhanarslan , @svenchio  and @Thomaslleblanc   ? Let us know if you’re still facing the same issue we’ll be happy to assist you further.

Regards,

Dinesh

[v-dineshya]

Hi @Pravin_Suwasiya ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

Regards,

Dinesh

[cengizhanarslan]

In Fabric Git integration, the repo is meant to store text-based artifacts (TMDL / report.json / metadata). If you’re seeing pushes fail around 50–100 MB, that’s almost always a GitHub large-file limit issue, not Fabric itself.

• Do not store PBIX or other binaries in the Git-integrated repo

  • Keep the repo strictly for Fabric’s generated folders (semantic model / report definitions).

  • If someone is committing large files manually, move them out.

• Add a .gitignore for binaries
  Ignore typical culprits: *.pbix, *.pbit, *.zip, *.csv (if huge), *.parquet, large media, etc.

• Use Git LFS only if you truly must version big binaries

  • Git LFS is the GitHub-supported way to store files over the normal limits.

• Store large assets elsewhere

  • SharePoint/OneDrive, Azure Blob, ADLS/OneLake, or an internal artifact store

  • Repo stores references + deployment scripts, not the big file itself.

[svenchio]

Hi @Pravin_Suwasiya  but I think there's a very important question to answer here, you said "when the folder or file size increases (around 50–100 MB or more)." and I would ask why? I mean, the folders and content created for your report and semantic model are basically json files that consumes a few KB's worth of space, nonetheless, certain binary artifacts can grow big like embedded images, custom visuals assets, that most commonly are accidentally committed locally, one example: In PBIP projects, there’s a SemanticModel/.pbi/cache.abf (Analysis Services backup) that is local-only and should be ignored by Git; Fabric’s guidance notes this file is excluded by default via .gitignore, but if that rule is missing or overridden, it can exceed 100 MB... so, my first recoimmendatios is to identify what is taking so much space and if this is really neccesary of just stuff that is not supposed to be push/pull from GitHub. 

Quick checklist I would recommend... 

#1.  Confirm your repo ignores SemanticModel/.pbi/cache.abf and .pbi/localSettings.json.

#2. Install and enable LFS: git lfs install (once per user) 

#3. Migrate any already-committed large files to LFS: git lfs migrate import --include="path/to/file"; then push

Hope this helps and be a complement of what @tomtom  suggested with regards Enabling & tracking LFS

A thumbs-up would be nice if you find this info. useful and even better to mark as a solution, best of lucks 

[Pravin_Suwasiya]

Hi @svenchio 
Thanks for the prompt response. I tried the method you shared, but I am still facing the following errors.
1.on git bash
--> git push origin branch_name
error: authentication error : authentication requried : authorization error : https://github.com/org_name/repo.git/info/lfs/locks/verfity
check that you have proper access to the repository
error : failed to push some refs to 'https://github.com/org_name/repo.git/info/lfs/locks/verfity'

2.other type of error also used <git lfs push --all' origin branch_name> still get the same issue as above
Enumerating objects: 499, done.
Counting objects: 100% (499/499), done.
Delta compression using up to 8 threads
Compressing objects: 100% (296/296), done.
Writing objects: 100% (498/498), 52.96 KiB | 286.00 KiB/s, done.
Total 498 (delta 1), reused 8 (delta 0), pack-reused 0 (from 0)
remote: Resolving deltas: 100% (1/1), completed with 1 local object.
remote: error: GH008: Your push referenced at least 2 unknown Git LFS objects:
remote: 130395ed52a270679739fe1bf09decbf311d4d3ee103
remote: dcdc6467c748c171112b4500290fa9fd8f149442528d
remote: Try to push them with 'git lfs push --all'.
To https://github.com/org_name/repo.git
! [remote rejected] branch_name -> branch_name (pre-receive hook declined)
error: failed to push some refs to 'https://github.com/org_name/repo.git'

Even though I have admin access to both the organization and the repository, the issue still persists.
For Git LFS, token-based authentication is required. I have already configured this and am using the same token that is used for Fabric integration, but the problem continues.

below is error which i normally get:

1. on git desktop
Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.

2. on git bash

$ git push origin branch_name
Enumerating objects: 150, done.
Counting objects: 100% (150/150), done.
Delta compression using up to 8 threads
Compressing objects: 100% (108/108), done.
Writing objects: 100% (149/149), 113.75 KiB | 1.29 MiB/s, done.
Total 149 (delta 56), reused 4 (delta 0), pack-reused 0 (from 0)
error: RPC failed; HTTP 403 curl 22 The requested URL returned error: 403
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly
Everything up-to-date

Thanks in advance for your help.

[v-dineshya]

Hi @Pravin_Suwasiya ,

Thank you for the update.  It appears this issue might require deeper investigation from the Microsoft  Fabric support team. I recommend opening a Microsoft support ticket so they can trace the issue. To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Regards,

Dinesh

[v-dineshya]

Hi @Pravin_Suwasiya ,

We are following up to inquire whether you have raised the support ticket. If you have already done so, we kindly request you to share your feedback regarding the issue raised.In case a solution has been provided, we would be grateful if you could share it with the community. This will assist others facing similar challenges and benefit the wider community. If you need any more assistance, please feel free to connect with the Microsoft Fabric community.

Regards,

Dinesh

[svenchio]

Hi @Pravin_Suwasiya, I don't want to "ghost" you, but unfortunately GitHub is out of my areas of expertise 😓 ...  this seems to be related to specific permission needed in that platform wich I'm not remotly familiar with  ... I'm much closer to DevOps repositories; but I'm sure there's many people in this communicty with the neccesary expertise to help out! Best of lucks mate and wish your issue get's resolve. 

[Thomaslleblanc]

You can try enabling Large FIle Storage for git
git lfs install

git lfs track "*.pbip"

git lfs track "*.json"

git add .gitattributes

git commit -m "Enable GIT LFS for Fabric files"

git push origin main

Note: GitHub still enforces a 2 GB repo size limit and individual file limit of 2 GB with LFS.