Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New repositories have all pull request options disabled. #3952

Closed
de-vri-es opened this issue May 11, 2018 · 6 comments · Fixed by #4369
Closed

New repositories have all pull request options disabled. #3952

de-vri-es opened this issue May 11, 2018 · 6 comments · Fixed by #4369
Labels
Milestone

Comments

@de-vri-es
Copy link

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.

@lunny lunny added the type/question Issue needs no code to be fixed, only a description on how to fix it yourself. label May 11, 2018
@lafriks
Copy link
Member

lafriks commented May 11, 2018

Do you create that form UI or API?

@de-vri-es
Copy link
Author

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

@pjanx
Copy link

pjanx commented 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.

@lunny
Copy link
Member

lunny commented Jun 26, 2018

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

@de-vri-es
Copy link
Author

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?

@lafriks lafriks added type/bug and removed type/question Issue needs no code to be fixed, only a description on how to fix it yourself. labels Jul 4, 2018
@lafriks lafriks added this to the 1.5.0 milestone Jul 4, 2018
@de-vri-es
Copy link
Author

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

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants