github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-15 20:09:18 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

add option to deactivate Update branch button #8353

New Issue
Closed
opened 2025-11-02 08:03:26 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-02 08:03:26 -06:00
Owner
Copy Link

Originally created by @JHenneberg on GitHub (Jan 14, 2022).

Feature Description

Because it is not possible by now to set the update strategy for the update branch button it would be quite usefull to be able to deactivate it completly to avoid using it with a not intended strategy.

Of course the best solution would be too define the update strategy.

Screenshots

No response

Originally created by @JHenneberg on GitHub (Jan 14, 2022). ### Feature Description Because it is not possible by now to set the update strategy for the `update branch` button it would be quite usefull to be able to deactivate it completly to avoid using it with a not intended strategy. Of course the best solution would be too define the update strategy. ### Screenshots _No response_
GiteaMirror added the type/feature label 2025-11-02 08:03:26 -06:00
GiteaMirror commented 2025-11-02 08:03:27 -06:00
Author
Owner
Copy Link

@Ulrik-dk commented on GitHub (Sep 8, 2022):

update branch is very ambiguous until you try, and then find out that you are merging master into your feature branch.

Would be nice to be able to rebase on master.

@Ulrik-dk commented on GitHub (Sep 8, 2022): `update branch` is very ambiguous until you try, and then find out that you are merging master into your feature branch. Would be nice to be able to rebase on master.
GiteaMirror commented 2025-11-02 08:03:27 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Sep 8, 2022):

You can rebase if you want too

@6543 commented on GitHub (Sep 8, 2022): You can rebase if you want too
GiteaMirror commented 2025-11-02 08:03:27 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Sep 8, 2022):

What version do you use?!?

@6543 commented on GitHub (Sep 8, 2022): What version do you use?!?
GiteaMirror commented 2025-11-02 08:03:28 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Sep 8, 2022):

... Of course the best solution would be too define the update strategy. ...

Can be done closing

@6543 commented on GitHub (Sep 8, 2022): ... Of course the best solution would be too define the update strategy. ... Can be done closing
GiteaMirror commented 2025-11-02 08:03:28 -06:00
Author
Owner
Copy Link

@Ulrik-dk commented on GitHub (Sep 8, 2022):

@6543 I can see that I am using 1.15.10, and that the latest is 1.17.2. That would explain it.

@Ulrik-dk commented on GitHub (Sep 8, 2022): @6543 I can see that I am using 1.15.10, and that the latest is 1.17.2. That would explain it.
GiteaMirror commented 2025-11-02 08:03:28 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Sep 8, 2022):

@Ulrik-dk keep in mind of breaking changes, they are written in changelogs for v1.16.0 and v1.17.0 ... please upgrade asap as there are known sec-issues

@6543 commented on GitHub (Sep 8, 2022): @Ulrik-dk keep in mind of breaking changes, they are written in changelogs for v1.16.0 and v1.17.0 ... please upgrade asap as there are known sec-issues
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/feature
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#8353
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?