github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

AGit PR creation with LFS objects #14537

New Issue
Open
opened 2025-11-02 11:15:36 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 11:15:36 -06:00
Owner
Copy Link

Originally created by @AdamMajer on GitHub (Jun 2, 2025).

Feature Description

Currently, it's impossible to create PRs with LFS objects if you do not have write access to target repository,

> git push origin HEAD:refs/for/main/foobar
Remote "origin" does not support the Git LFS locking API. Consider disabling it with:
  $ git config lfs.https://demo.gitea.com/gnuman/test.git/info/lfs.locksverify false
batch request: error::   0% (0/1), 0 B | 0 B/s                                                                               
error: User: 1460:adamm2 with Key: 37:t is not authorized to write to gnuman/test.
error:: exit status 1
error: failed to push some refs to 'demo.gitea.com:gnuman/test.git'

Screenshots

No response

Originally created by @AdamMajer on GitHub (Jun 2, 2025). ### Feature Description Currently, it's impossible to create PRs with LFS objects if you do not have write access to target repository, ``` > git push origin HEAD:refs/for/main/foobar Remote "origin" does not support the Git LFS locking API. Consider disabling it with: $ git config lfs.https://demo.gitea.com/gnuman/test.git/info/lfs.locksverify false batch request: error:: 0% (0/1), 0 B | 0 B/s error: User: 1460:adamm2 with Key: 37:t is not authorized to write to gnuman/test. error:: exit status 1 error: failed to push some refs to 'demo.gitea.com:gnuman/test.git' ``` ### Screenshots _No response_
GiteaMirror added the type/proposal label 2025-11-02 11:15:36 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#14537
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?