404 error when Pull to repo with 'pull requests' disabled #10671

New Issue

GiteaMirror · 2025-11-02T09:14:59-06:00

GiteaMirror commented

2025-11-02 09:14:59 -06:00

Originally created by @barzog on GitHub (Apr 17, 2023).

Description

When we fork repo - forked repo is created with 'pull request' repo setting enabled. Old repo 'pull request' setting is left untouched. When we trying to create pull request from new repo to old repo we receive 404 'Not found' error if 'pull request' setting is disabled in old repo settings. More informative message is needed, or (more better) only repos with 'pull requests' enabled should shown in 'merge into' drop-down list.

Gitea Version

1.19.1

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

Git Version

No response

Operating System

Flatcar

How are you running Gitea?

Kubernetes helm-chart on k3s running on flatcar linux.

Database

PostgreSQL

Originally created by @barzog on GitHub (Apr 17, 2023). ### Description When we fork repo - forked repo is created with 'pull request' repo setting enabled. Old repo 'pull request' setting is left untouched. When we trying to create pull request from new repo to old repo we receive 404 'Not found' error if 'pull request' setting is disabled in old repo settings. More informative message is needed, or (more better) only repos with 'pull requests' enabled should shown in 'merge into' drop-down list. ### Gitea Version 1.19.1 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots ![image](https://user-images.githubusercontent.com/11497626/232467800-41aa1f93-8db6-44bd-a62d-2d7ead020de9.png) ### Git Version _No response_ ### Operating System Flatcar ### How are you running Gitea? Kubernetes helm-chart on k3s running on flatcar linux. ### Database PostgreSQL

GiteaMirror added the type/bug label 2025-11-02 09:14:59 -06:00

GiteaMirror closed this issue

2025-11-02 09:14:59 -06:00

GiteaMirror commented

2025-11-02 09:15:00 -06:00

@lunny commented on GitHub (Apr 18, 2023):

So should we allow repo to be forked if pull request siabled? 🤔

@lunny commented on GitHub (Apr 18, 2023): So should we allow repo to be forked if pull request siabled? 🤔

GiteaMirror commented

2025-11-02 09:15:00 -06:00

@barzog commented on GitHub (Apr 18, 2023):

This may be even better (but I think that fork button should be shown anyway, but either in 'grayed' state - to show end-user that functionality is there but disabled or in 'normal' state with warning that 'you should enable PR on this repo beforehand.

@barzog commented on GitHub (Apr 18, 2023): This may be even better (but I think that fork button should be shown anyway, but either in 'grayed' state - to show end-user that functionality is there but disabled or in 'normal' state with warning that 'you should enable PR on this repo beforehand.

GiteaMirror commented

2025-11-02 09:15:00 -06:00

@silverwind commented on GitHub (Apr 18, 2023):

So should we allow repo to be forked if pull request siabled? 🤔

Absolutely not. Not all forks are for the purpose as a source of pull requests, they might become separate projects etc.

@silverwind commented on GitHub (Apr 18, 2023): > So should we allow repo to be forked if pull request siabled? 🤔 Absolutely not. Not all forks are for the purpose as a source of pull requests, they might become separate projects etc.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#10671