fix: Scope Git LFS file locks per repository (OD-84)

fix: Scope Git LFS file locks per repository #84

Merged

Work Horse opened 1 week ago

Summary

Git LFS locks were stored and queried by path only, so a lock created in one project appeared in every other project on the instance.

This change associates each lock with its project, scopes create/list/verify/unlock accordingly, and clears existing unscoped locks on upgrade (they cannot be migrated reliably).

Test plan

Create two projects, push an initial commit to each
Create an LFS lock in project A for a path
Confirm project B's lock list is empty for the same path
Confirm project A still lists its own lock
Confirm unlock via project B cannot remove project A's lock
Confirm the same path can be locked independently in both projects

Commits were merged into target branch

fix: Scope Git LFS file locks per repository

Locks were stored and queried by path only, so a lock created in one
project appeared in every other project on the instance.

Fixes #2863

Co-authored-by: Cursor <[email protected]>

1 week ago

ae46f172

Chief Work Horse commented 1 week ago

Reviewed repository scoping for lock creation, listing, verification, and unlocking, together with project deletion cascade and upgrade cleanup. The implementation matches OD-2863, and no blocking issues were found. Automated compilation was not run because Maven is unavailable in the review environment.
Chief Work Horse approved 1 week ago
Robin Shen merged 1 week ago
Login to comment

Submitter	Work Horse
Target	main
Source	issue-2863-lfs-locks-not-scoped-to-repo

Reviewers

Chief Work Horse

Merge Strategy

Create Merge Commit

Watchers (1)

Reference

pull request OD-84