Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Git LFS File Locking API #2725

Closed
2 of 7 tasks
flozz opened this issue Oct 17, 2017 · 3 comments · Fixed by #2938
Closed
2 of 7 tasks

Git LFS File Locking API #2725

flozz opened this issue Oct 17, 2017 · 3 comments · Fixed by #2938
Assignees
Labels
type/enhancement An improvement of existing functionality
Milestone

Comments

@flozz
Copy link

flozz commented Oct 17, 2017

  • Gitea version (or commit ref): 1.2.0
  • Git version: 2.11.0
  • Operating system: Debian 9
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist: -

Description

Hi,

The Git LFS File Locking API is currently not implemented in Gitea:

$ git lfs lock foo.bin
Lock failed: Repository or object not found: http://git.example.com/test/test.git/info/lfs/locks
Check that it exists and that you have proper access to it

I wonder if there is a plan to support it or even if someone is interested by it?

@lunny lunny added the type/enhancement An improvement of existing functionality label Oct 17, 2017
@lunny lunny added this to the 1.x.x milestone Oct 17, 2017
@OmarAssadi
Copy link
Contributor

or even if someone is interested by it?

Useful feature, IMO! Added a tiny starting bounty to this one.

current amount

@sapk
Copy link
Member

sapk commented Oct 26, 2017

I could take that one if no one is on it. ^^

@lunny
Copy link
Member

lunny commented Oct 26, 2017

@sapk please do it.

This was referenced Nov 19, 2017
@lafriks lafriks modified the milestones: 1.x.x, 1.4.0 Nov 28, 2017
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/enhancement An improvement of existing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants