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

error upgrade #3795

New Issue
Closed
opened 2025-11-02 05:25:29 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 05:25:29 -06:00
Owner
Copy Link

Originally created by @bajins on GitHub (Aug 16, 2019).

need to replace the binary file name after the upgrade, otherwise there will be an error in the push!

can be solved with commandsc

grep -rl "gitea-1.8-linux-amd64" ./* | xargs sed -i s/"gitea-1.8-linux-amd64"/"gitea-1.9.0-linux-amd64"/g
Originally created by @bajins on GitHub (Aug 16, 2019). need to replace the binary file name after the upgrade, otherwise there will be an error in the push! can be solved with commandsc ```bash grep -rl "gitea-1.8-linux-amd64" ./* | xargs sed -i s/"gitea-1.8-linux-amd64"/"gitea-1.9.0-linux-amd64"/g ```
GiteaMirror commented 2025-11-02 05:25:29 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Aug 16, 2019):

Thank you for commenting this :)

There is a built in utility in Gitea that does this, if you go to admin dashboard and run the "Resynchronize pre-receive, update and post-receive hooks of all repositories." task.

@techknowlogick commented on GitHub (Aug 16, 2019): Thank you for commenting this :) There is a built in utility in Gitea that does this, if you go to admin dashboard and run the "Resynchronize pre-receive, update and post-receive hooks of all repositories." task.
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
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#3795
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?