New repositories have all pull request options disabled. #1778

New Issue

GiteaMirror · 2025-11-02T04:12:58-06:00

GiteaMirror commented

2025-11-02 04:12:58 -06:00

Originally created by @de-vri-es on GitHub (May 11, 2018).

We recently updated gitea. One of the new features this introduced is the option to disable specific pull request merge strategies (merge, rebase, squash).

All old repositories have all of these options available. However, every new repository we create has all of them disabled. I also couldn't find a way to set defaults globally.

We have quite a few repositories, so manually having to enable these options is rather a nuisance. Did I miss something? If not I believe that a global default for this would be very useful. Alternatively, simply having them all enabled by default is also good for us.

Originally created by @de-vri-es on GitHub (May 11, 2018). We recently updated gitea. One of the new features this introduced is the option to disable specific pull request merge strategies (merge, rebase, squash). All old repositories have all of these options available. However, every new repository we create has all of them disabled. I also couldn't find a way to set defaults globally. We have quite a few repositories, so manually having to enable these options is rather a nuisance. Did I miss something? If not I believe that a global default for this would be very useful. Alternatively, simply having them all enabled by default is also good for us.

GiteaMirror added the type/bug label 2025-11-02 04:12:58 -06:00

GiteaMirror closed this issue

2025-11-02 04:12:59 -06:00

GiteaMirror commented

2025-11-02 04:12:59 -06:00

@lafriks commented on GitHub (May 11, 2018):

Do you create that form UI or API?

@lafriks commented on GitHub (May 11, 2018): Do you create that form UI or API?

GiteaMirror commented

2025-11-02 04:13:00 -06:00

@de-vri-es commented on GitHub (May 11, 2018):

This was directly from the web interface. I didn't try with the API.

@de-vri-es commented on GitHub (May 11, 2018): This was directly from the web interface. I didn't try with the API.

GiteaMirror commented

2025-11-02 04:13:00 -06:00

@pjanx commented on GitHub (Jun 26, 2018):

I have used the API with the same results, and I haven't been able to find an API endpoint to change it.

@pjanx commented on GitHub (Jun 26, 2018): I have used the API with the same results, and I haven't been able to find an API endpoint to change it.

GiteaMirror commented

2025-11-02 04:13:00 -06:00

@lunny commented on GitHub (Jun 26, 2018):

You have to change it on the UI currently as I know.

@lunny commented on GitHub (Jun 26, 2018): You have to change it on the UI currently as I know.

GiteaMirror commented

2025-11-02 04:13:00 -06:00

@de-vri-es commented on GitHub (Jul 4, 2018):

Would it be an option to simply set the defaults to true until someone has the time to implement configurable defaults? It would improve usability a lot for me.

I wanted to submit a PR for this, but I got quite confused by Go, and I don't have the time to learn it sadly. But I imagine changing a default is a simple patch?

@de-vri-es commented on GitHub (Jul 4, 2018): Would it be an option to simply set the defaults to true until someone has the time to implement configurable defaults? It would improve usability a lot for me. I wanted to submit a PR for this, but I got quite confused by Go, and I don't have the time to learn it sadly. But I imagine changing a default is a simple patch?

GiteaMirror commented

2025-11-02 04:13:00 -06:00

@de-vri-es commented on GitHub (Jul 5, 2018):

@lafriks: awesome, thanks! 👍 And @lunny for the quick review.

@de-vri-es commented on GitHub (Jul 5, 2018): @lafriks: awesome, thanks! :+1: And @lunny for the quick review.

GiteaMirror referenced this issue

2025-11-02 12:01:08 -06:00

[PR #1778] [MERGED] Make side nav on dashboard stackable #16049

Sign in to join this conversation.