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

proper way to disable force push? #3158

New Issue
Closed
opened 2025-11-02 05:02:18 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 05:02:18 -06:00
Owner
Copy Link

Originally created by @erpadmin on GitHub (Apr 8, 2019).

Is this the proper way to global disable force pushing for gitea?

git config --system receive.denyNonFastForwards true
Originally created by @erpadmin on GitHub (Apr 8, 2019). Is this the proper way to global disable force pushing for gitea? ``` git config --system receive.denyNonFastForwards true ```
GiteaMirror added the type/question label 2025-11-02 05:02:18 -06:00
GiteaMirror commented 2025-11-02 05:02:19 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Apr 8, 2019):

That will disable force push on client side. To disable in gitea you need to use branch protection

@lafriks commented on GitHub (Apr 8, 2019): That will disable force push on client side. To disable in gitea you need to use branch protection
GiteaMirror commented 2025-11-02 05:02:20 -06:00
Author
Owner
Copy Link

@erpadmin commented on GitHub (Apr 10, 2019):

The current design is not clear.

Enable Branch Protection description is "Prevent deletion and disable Git force pushing to the branch." In practice this option requires that Enable Push Whitelist is enabled and users are added in order to do a fast-forward push.

Should the description be updated? Or an independent option to specifically disable force pushing only be added?

@erpadmin commented on GitHub (Apr 10, 2019): The current design is not clear. Enable Branch Protection description is "Prevent deletion and disable Git force pushing to the branch." In practice this option requires that Enable Push Whitelist is enabled and users are added in order to do a fast-forward push. Should the description be updated? Or an independent option to specifically disable force pushing only be added?
GiteaMirror commented 2025-11-02 05:02:20 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 11, 2019):

@erpadmin Please send a PR to fix that doc.

@lunny commented on GitHub (Apr 11, 2019): @erpadmin Please send a PR to fix that doc.
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/question
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#3158
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?