- Is LFS triggered by a file size that Atlassian/Bitbucket sets ?
- Or maybe Bitbucket uses LFS : as just there waiting for us to tell what files to handle no matter their size ?
....or maybe we're disallowed to know.. ??
I saw an "example" in the 19th doc I read, where 4MB was stated.. but never was there a doc found that stated a specific size for a trigger NOR stating we control the trigger size based on filetype without regards to size(which would be srsly lame). I've looked for 1+Hour..I have a headache to prove this.
Clearly I am frustrated..I don't think I have ever encountered anything like this in 20 years of working countless industry. I feel like I'm sifting through hot spaghetti in the dark to find the colored noodle that isn't there.
I'm not an expert in this, but haven't seen file size trigger anywhere in the docs.
Would guess, since it is not (yet) supported in the extension itself, it's unlikely that Bitbucket does.
Atlassian tutorial covers how you tell Git LFS which files to track here: https://www.atlassian.com/git/tutorials/git-lfs#tracking-files
For example, tell Git LFS to track all files matching the *.bin pattern:
git lfs track '*.bin'
Git LFS Roadmap link: https://github.com/git-lfs/git-lfs/blob/master/ROADMAP.md
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot