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

500 error creating pull request #4046

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

Originally created by @bkmgit on GitHub (Oct 2, 2019).

  • Gitea version (or commit ref): Gitea 1.9.3
  • Git version: 1.8.3.1
  • Operating system: Cent OS 7
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MariaDB
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:
    Not sure what to put here. Log contains only SQL command history.

Description

500 error obtained when trying to merge a pull request through the web interface. It is possible to merge the pull requests using the command line on a different computer, for example following

and then pushing the changes.

Specifically, within the main repository one is working in, one can:

git remote add somefork https://my.gitea.ip:3000/cool/fork
git fetch somefork
git checkout master
git merge somefork/master
git push

Old related issues include #5253 #1434 #6460 #7636
...

Screenshots

Originally created by @bkmgit on GitHub (Oct 2, 2019). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): Gitea 1.9.3 - Git version: 1.8.3.1 - Operating system: Cent OS 7 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [X] MariaDB - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [X] No - [ ] Not relevant - Log gist: Not sure what to put here. Log contains only SQL command history. ## Description 500 error obtained when trying to merge a pull request through the web interface. It is possible to merge the pull requests using the command line on a different computer, for example following * http://www.bartread.com/2014/02/12/git-basics-how-to-merge-changes-from-a-different-fork-into-your-own-branch/ * https://stackoverflow.com/questions/6022302/how-to-apply-unmerged-upstream-pull-requests-from-other-forks-into-my-fork and then pushing the changes. Specifically, within the main repository one is working in, one can: git remote add somefork https://my.gitea.ip:3000/cool/fork git fetch somefork git checkout master git merge somefork/master git push Old related issues include #5253 #1434 #6460 #7636 ... ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror commented 2025-11-02 05:35:30 -06:00
Author
Owner
Copy Link

@guillep2k commented on GitHub (Oct 2, 2019):

There are some important incompatibilities in git versions prior to 1.9.0. Check Gitea's README. Please consider upgrading git.

@guillep2k commented on GitHub (Oct 2, 2019): There are some important incompatibilities in git versions prior to 1.9.0. Check [Gitea's README](https://docs.gitea.io/en-us/#system-requirements). Please consider upgrading git.
GiteaMirror commented 2025-11-02 05:35:31 -06:00
Author
Owner
Copy Link

@bkmgit commented on GitHub (Oct 3, 2019):

Thanks, upgrading git resolved the issue.

@bkmgit commented on GitHub (Oct 3, 2019): Thanks, upgrading git resolved the issue.
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#4046
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?