[FEATURE] Add option to Disable Background Lock File System (LFS) requests

[Tristan-c74]

1. Background

We are using an "On Premise" Git repository which does not support GIT Lock File System (LFS)

Due to Git Graph polling the server every few minutes, I get continuous pop up errors:

It would be very helpful to have an option to disable the LFS polling requests to origin servers

2. Proposed Solution

Add a new setting for Git Graph+:
"Fetch LFS Locks" : Enable / Disable checkbox
When disabled, cease polling the origin server for File Lock status

3. Affected Area

Check all that apply.

• Commit graph (Graph View)
• Commit details panel (Bottom Panel)
• Sidebar (Branches / Remotes / Tags / Stashes / Worktrees)
• Toolbar (Fetch / Pull / Push / Refresh)
• Context menu
• Search
• Statistics view (Stats)
• Activity Log
• i18n (localization)
• Git operations (new Git command support)
• Other

4. Alternatives or References

An alternative to the config setting, is to examine the current Git config for the open Repository, and look for the git config setting "lfs.locksverify"
When set by the the Git command such as: "git config lfs.locksverify false", the Git Repo is configured to not request LFS settings from Origin server. Git Graph+ could be made to respect that setting automatically.

[reza-hw]

I am experiencing the same issue with Git Graph+ 0.7.3.

In my case, the repository is hosted on an on-prem Bitbucket Server that does not implement the Git LFS locking endpoint. Git Graph+ repeatedly shows:

Git Graph+: LFS locks failed: Error while retrieving locks: Not Implemented:
http://<git-server>/scm/<project>/<repository>.git/info/lfs/locks?refspec=refs%2Fheads%2Fmaster

The server returns HTTP 501 Not Implemented for the LFS locks endpoint.

The warning appears repeatedly every few seconds, while the repository and normal Git operations otherwise work correctly.

Environment:

• VS Code: 1.107.0
• Git Graph+: 0.7.3
• Git: 2.43.0.windows.1
• Git LFS: git-lfs/3.4.0
• Git server: Bitbucket Server (on-prem)
• OS: Windows
• Repository remote protocol: HTTP

Regarding the lfs.locksverify=false alternative mentioned above: according to the Git LFS documentation, locksverify controls lock verification performed by the Git LFS pre-push hook. Setting it to false causes the pre-push hook to skip the lock verification request.

Git Graph+'s background request in this case is different: it is listing locks through the /info/lfs/locks endpoint. Therefore, setting lfs.locksverify=false by itself does not appear to prevent Git Graph+ from making these background lock-list requests unless Git Graph+ is explicitly changed to use that setting as a signal.

I agree that adding an option to disable LFS lock polling would solve the problem. Another useful behavior would be for Git Graph+ to detect HTTP 501 Not Implemented, treat LFS locking as unsupported for that repository, and stop polling the endpoint.

That would avoid repeated warning notifications for servers that support Git/LFS storage but not the optional LFS locking API.