pull request to a template repository #5005

New Issue

GiteaMirror · 2025-11-02T06:10:44-06:00

GiteaMirror commented

2025-11-02 06:10:44 -06:00

Originally created by @yee379 on GitHub (Mar 6, 2020).

Gitea version (or commit ref): 1.11.1
Git version:
Operating system: dockerhub image
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- [ X ] SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- [ X ] Not relevant
Log gist:

Description

I'm making use of 'Make a repository a template'; there are cases where the new repos that are created with this Template has modifications that i would like to merge back 'upstream'. however, there appears to be no way to do this via the 'Pull Requests' -> 'New Pull Request'.

Originally created by @yee379 on GitHub (Mar 6, 2020). - Gitea version (or commit ref): 1.11.1 - Git version: - Operating system: dockerhub image - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ X ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [ X ] Not relevant - Log gist: ## Description I'm making use of 'Make a repository a template'; there are cases where the new repos that are created with this Template has modifications that i would like to merge back 'upstream'. however, there appears to be no way to do this via the 'Pull Requests' -> 'New Pull Request'.

GiteaMirror added the issue/stale label 2025-11-02 06:10:44 -06:00

GiteaMirror closed this issue

2025-11-02 06:10:45 -06:00

GiteaMirror commented

2025-11-02 06:10:46 -06:00

@jolheiser commented on GitHub (Mar 6, 2020):

In this case you should fork the template repo and make a PR with changes.

Repos generated from the template aren't necessarily intended to stay true to the template repo itself and thus aren't usually considered targets for merges.

@jolheiser commented on GitHub (Mar 6, 2020): In this case you should fork the template repo and make a PR with changes. Repos generated from the template aren't necessarily intended to stay true to the template repo itself and thus aren't usually considered targets for merges.

GiteaMirror commented

2025-11-02 06:10:46 -06:00

@stale[bot] commented on GitHub (May 5, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (May 5, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:10:46 -06:00

@stale[bot] commented on GitHub (May 19, 2020):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (May 19, 2020): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 09:27:58 -06:00

OAuth2 Error 500 UserSignIn No Matching Session #11112

GiteaMirror referenced this issue

2025-11-02 10:52:38 -06:00

500 upon authentik OAuth2/OpenID: login #13769

Sign in to join this conversation.