Git LFS v2.6.0 is now available
Git LFS v2.6.0 comes with a more robust authentication mechanism, new options to `git lfs checkout`, a handful of bug fixes, new platforms, and more.
![](https://github.blog/wp-content/uploads/2018/11/47938421-40057300-dea1-11e8-91c5-8abe2b7248c7.png?resize=1600%2C850)
A new version of Git LFS, the open source Git extension for versioning large files, is now available. Git LFS v2.6.0 comes with a more robust authentication mechanism, new options to git lfs checkout
, a handful of bug fixes, new platforms, and more.
Authentication improvements
Git LFS can make two types of HTTP(s) requests: API requests (which allow the client to retrieve any metadata it might need), and storage requests (which allow the client to upload or download data to external storage).
Previously, Git LFS would determine how it should authenticate LFS API requests, then use the same method to authenticate transfer requests. However, API requests and transfer requests generally go to different places and aren’t guaranteed to require the same authentication method.
Git LFS now treats those requests as requiring different authentication and will determine the correct mode for each.
New git lfs checkout
options
Git is designed to handle merge conflicts as best it can without the need for human intervention, but often it’s built-in merge facilities do not resolve conflicts correctly for large files. When that’s the case, it can be useful to compare the contents of both sides of the conflict by hand.
git lfs checkout
now provides convenient options for doing just that: you can ask it to resolve “our” side of a merge, “their” side, or the merge base. Here’s an example:
$ git lfs checkout --ours --to=conflict.psd.ours -- conflict.psd
$ git lfs checkout --theirs --to=conflict.psd.theirs -- conflict.psd
$ git lfs checkout --base --to=conflict.psd.base -- conflict.psd
$ ls -la
-rw-r--r--@ 1 user group 16789 Oct 22 18:59 conflict.psd.base
-rw-r--r--@ 1 user group 19810 Oct 22 18:59 conflict.psd.ours
-rw-r--r--@ 1 user group 18303 Oct 22 18:59 conflict.psd.theirs
From here, you can open each side of the conflict and resolve the differences however you see fit.
And all of the rest
You’ll see a handful of other new features and bug fixes in v2.6.0 like new release targets including arm64, enhanced support for more configuration options from Git, and more.
For instructions on configuring Git LFS, read the documentation.
Tags:
Written by
Related posts
![](https://github.blog/wp-content/uploads/2023/10/Collaboration-DarkMode-2.png?resize=400%2C212)
2024 is the biggest global election year in history. What’s at stake for developers?
GitHub is considering what is at stake for our users and platform, how we can take responsible action to support free and fair elections, and how developers contribute to resilient democratic processes.
![](https://github.blog/wp-content/uploads/2023/10/AI-DarkMode-2.png?resize=400%2C212)
GitHub named a Leader in the Gartner first-ever Magic Quadrant for AI Code Assistants
This year, as part of its annual Magic Quadrant series, Gartner published a first-of-its-kind report analyzing the state of play in the AI Code Assistants market–and named GitHub a Leader.
![AI in software development 2024 survey results with colorful graphics and percentages.](https://github.blog/wp-content/uploads/2024/08/ai-survey-header.png?resize=400%2C212)
Survey: The AI wave continues to grow on software development teams
We surveyed 2,000 people on software development teams at enterprises in the U.S., Brazil, India, and Germany about the use, experience, and expectations around generative AI tools in software development.