After migrating the data to LFS and promoted all LFS files (which is mentioned in .gitattributes) I could see that .zip extensions have a link which is pointing to LFS endpoint but .ico files do not have any link for endpoint and visible from UI. As both extensions (.zip & .ico) have a LOCK button so I am not able to understand this behavior. I need clarity on this, why Bitbucket is showing different behavior for this if both extensions are added in .gitattributes file and trackable by LFS?
As per Atlassian’s support team, the icon file is a small image in which both the browser and Bitbucket Server able to process the outcome, however, this is not the same for zip file since this is a binary file.
But still, I am not sure why .zip files have a link to LFS but .ico doesn’t have.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.