> git config core.sparsecheckout # timeout=10 > git fetch -no-tags -force -progress -prune - +refs/heads/test:refs/remotes/origin/test > git config -add +refs/heads/test:refs/remotes/origin/test # timeout=10 > git fetch -no-tags -force -progress - +refs/heads/test:refs/remotes/origin/testĬhecking out Revision 7888fec2200a056b081a077d0ec5c3023b18c70f (test)
#GIT LFS NOT PULLING FILES PASSWORD#
Using GIT_ASKPASS to set credentials GitHub Username & Password > git init /home/jenkins/agent/workspace/test # timeout=10 Hope this helps, let me know if there are any issues.Cloning with configured refspecs honoured and without tags Once the above steps have been performed, ask them to try to perform the git lfs fetch without the lfs path included - as this is not required and can cause issues when trying to locate the remote repo location: git lfs fetch origin main
#GIT LFS NOT PULLING FILES HOW TO#
Once this is done, I would suggest having them also ensure that git lfs is definitely installed on their local repository by running the following command, as if it is not - any git lfs commands will not work as GIT will not understand how to pull the data: git lfs install If the user is having issues fetching lfs content over HTTPS, I would suggest that they first ensure that the remote URL has been updated to include the App Password to avoid any potential authentication issues: git remote set-url origin the clone command is using the App Password, but their remote URL is not updated - this would explain why they are able to clone but not able to pull. The final confusing part, the user has been able to successfully clone other repositories with lfs tracked assets and have no problems pulling down these assets. We tried duplicating the project and uploading a new copy of the repository to bitbucket and the same issue occurs when they clone the repository.
This member also in the same user groups on bitbucket for access to repositories and permissions.
This issue is only affecting one member in the team and other team members have no problems pulling down the lfs tracked assets.
When inspecting these assets, the change to the files resembles that of an asset deletion. If we try to discard the changes, we get the following response from git.īatch response: Repository or object not found: Ĭheck that it exists and that you have proper access to itĮrror: failed to fetch some objects from ' 'įrom reading that message, it appears to be an authentication issue but if there was a successful clone of the main repository, you'd think the authentication would also be valid for the lfs content. The repository is able to successfully cloned however all of the assets marked to be tracked by git lfs are marked as changed. The repository is accessed via the https protocol along with app password. One of the team's developers are having problems pulling down the git lfs content from a bitbucket repository after cloning the repository.
0 kommentar(er)
