add the git lfs lock to GitHub repo lfs

[photonest3]

🏷️ Discussion Type

Product Feedback

Body

Describe the issue
A clear and concise description of why you wrote in today.
https://github.com/photonest3/Community.git/info/lfs/locks/verify

Remote "origin" does not support the Git LFS locking API. Consider disabling it with:
$ git config lfs.https://github.com/photonest3/Community.git/info/lfs.locksverify false
Post "https://github.com/photonest3/Community.git/info/lfs/locks/verify": EOF

System environment
The version of your operating system, plus any relevant information about platform or configuration (e.g., container or CI usage, Cygwin, WSL, or non-Basic authentication). If relevant, include the output of git config -l as a code block.
Windows 11 Powershell
Chocolatey git，etc

Output of git lfs env
The output of running git lfs env as a code block.
git-lfs/3.7.1 (GitHub; windows amd64; go 1.25.1; git git-lfs/git-lfs@b84b338)
git version 2.55.0.windows.3

Endpoint=https://github.com/photonest3/Community.git/info/lfs (auth=basic)
Endpoint (china)=https://gitee.com/photonest3/community.git/info/lfs (auth=none)
LocalWorkingDir=D:\Community
LocalGitDir=D:\Community.git
LocalGitStorageDir=D:\Community.git
LocalMediaDir=D:\Community.git\lfs\objects
LocalReferenceDirs=
TempDir=D:\Community.git\lfs\tmp
ConcurrentTransfers=8
TusTransfers=false
BasicTransfersOnly=false
SkipDownloadErrors=false
FetchRecentAlways=false
FetchRecentRefsDays=7
FetchRecentCommitsDays=0
FetchRecentRefsIncludeRemotes=true
PruneOffsetDays=3
PruneVerifyRemoteAlways=false
PruneVerifyUnreachableAlways=false
PruneRemoteName=origin
LfsStorageDir=D:\Community.git\lfs
AccessDownload=basic
AccessUpload=basic
DownloadTransfers=basic,lfs-standalone-file,ssh
UploadTransfers=basic,lfs-standalone-file,ssh
GIT_EXEC_PATH=C:/Program Files/Git/mingw64/libexec/git-core
git config filter.lfs.process = "git-lfs filter-process"
git config filter.lfs.smudge = "git-lfs smudge -- %f"
git config filter.lfs.clean = "git-lfs clean -- %f"

Additional context
Any other relevant context about the problem here.
since git lfs lock feature is made in 2017, so the problem need be solved by the git and github relation group.
because github user big, and git lfs lock return 405 or EOF is not happy.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[alexliluz]

GitHub does support Git LFS file locking, so an EOF from this request does
not by itself mean that GitHub lacks the locking API.

There are two separate Git LFS operations here:

1. transferring LFS objects;
2. checking locks before a push.

.../info/lfs/locks/verify is the second operation. The Git LFS locking
specification requires a POST request with LFS JSON headers and push
authentication. If the 405 came from opening that URL in a browser, that is
not a valid test because a browser sends GET. The Git LFS client is the right
way to test the endpoint.

If this repository does not use file locking

Use the client-suggested setting, but scope it to this clone rather than
setting it globally:

git config --local lfs.https://github.com/photonest3/Community.git/info/lfs.locksverify false
git config --local --get lfs.https://github.com/photonest3/Community.git/info/lfs.locksverify

The second command should print false.

This setting skips only the pre-push lock check. It does not disable Git
LFS object upload or download. The official Git LFS configuration reference
specifically recommends false when file locking is not being used or the
server enforces locks itself.

To undo the repository-local workaround:

git config --local --unset lfs.https://github.com/photonest3/Community.git/info/lfs.locksverify

If the team does use git lfs lock

Do not disable verification. Diagnose the connection/authentication path
instead:

git remote get-url origin
git config --show-origin --get-regexp "lfs\..*locksverify"
git lfs env
git lfs locks --remote=origin

Your git lfs env shows both a GitHub endpoint and a second china endpoint.
Confirm that the failing push really uses origin and that no repository,
global, proxy, or .lfsconfig setting rewrites its LFS URL.

For one diagnostic run in PowerShell:

$env:GIT_TRACE = "1"
$env:GIT_CURL_VERBOSE = "1"
git lfs locks --remote=origin
Remove-Item Env:GIT_TRACE
Remove-Item Env:GIT_CURL_VERBOSE

Review the trace locally before sharing it and remove authorization headers,
cookies, tokens, usernames, and private proxy details. A raw EOF usually
means that the HTTP/TLS connection was closed before Git LFS received a valid
response; a proxy, TLS-inspection product, credential helper, or transient
network path can cause that. If the sanitized trace shows that Git LFS sent
the required request to GitHub and GitHub itself returned an unexpected
status, send the timestamp and GitHub request ID (if present) to GitHub
Support.

Official references:

• Git LFS File Locking API, including the POST /locks/verify contract:
  https://github.com/git-lfs/git-lfs/blob/main/docs/api/locking.md
• lfs.<url>.locksverify behavior and URL-scoped configuration:
  https://github.com/git-lfs/git-lfs/blob/main/docs/man/git-lfs-config.adoc
• GitHub announcement and example of Git LFS file locking:
  https://github.blog/open-source/git/git-lfs-2-0-0-released/