404 error when creating new branch in web interface with pull requests disabled #4057

Closed
opened 2025-11-02 05:35:56 -06:00 by GiteaMirror · 0 comments
Owner

Originally created by @bmerrison on GitHub (Oct 3, 2019).

  • Gitea version (or commit ref): 1.9.3 built with GNU Make 4.1, go1.12.9 : bindata, sqlite, sqlite_unlock_notify
  • Git version: 2.1.4
  • Operating system: Debian Jessie
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (not sure how to provide URL as you'd need to be added to my repo)
    • No
    • Not relevant

Description

Working Case:

  1. Ensure Pull Requests are enabled in a repository's settings.
  2. Manually edit a file using the web GUI. Choose to commit the change onto a new branch.
  3. The change is committed successfully onto a new branch.

Not-working Case:

  1. Ensure Pull Requests are disabled in a repository's settings.
  2. Manually edit a file using the web GUI. Choose to commit the change onto a new branch.
  3. The change is committed successfully onto a new branch but the page returns a 404:

image

This has only become an issue since upgrading from 1.8.0 to 1.9.3.

Originally created by @bmerrison on GitHub (Oct 3, 2019). - Gitea version (or commit ref): 1.9.3 built with GNU Make 4.1, go1.12.9 : bindata, sqlite, sqlite_unlock_notify - Git version: 2.1.4 - Operating system: Debian Jessie - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (not sure how to provide URL as you'd need to be added to my repo) - [ ] No - [ ] Not relevant ## Description ### Working Case: 1. Ensure Pull Requests are **enabled** in a repository's settings. 2. Manually edit a file using the web GUI. Choose to commit the change onto a new branch. 3. The change is committed successfully onto a new branch. ### Not-working Case: 1. Ensure Pull Requests are **disabled** in a repository's settings. 2. Manually edit a file using the web GUI. Choose to commit the change onto a new branch. 3. The change is committed successfully onto a new branch but the page returns a 404: ![image](https://user-images.githubusercontent.com/2444819/66131078-ac757e80-e5ea-11e9-9ce6-2578b2165b99.png) This has only become an issue since upgrading from 1.8.0 to 1.9.3.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#4057