github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 10:39:38 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

allow PullsAllowMerge/PullsAllowRebase to be enabled via configuration #1707

New Issue
Closed
opened 2025-11-02 04:10:20 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 04:10:20 -06:00
Owner
Copy Link

Originally created by @jstrachan on GitHub (Apr 18, 2018).

I wonder if we could add a configuration so that we can enable the flags PullsAllowMerge/PullsAllowRebase OOTB on all newly created repositories?

Then whether we create new repositories via the web UI or REST API they could come with some of these boxes enabled?

Otherwise its painful; folks have to go into the web UI and tweak newly created repos if they want them to work with PRs:
repo-config

I originally raised this as an issue against the REST API - but it turns out there isn't a REST API I can see to configure the repository options and this issue affects repos created via the web UI too
https://github.com/go-gitea/go-sdk/issues/100

Originally created by @jstrachan on GitHub (Apr 18, 2018). I wonder if we could add a configuration so that we can enable the flags `PullsAllowMerge/PullsAllowRebase` OOTB on all newly created repositories? Then whether we create new repositories via the web UI or REST API they could come with some of these boxes enabled? Otherwise its painful; folks have to go into the web UI and tweak newly created repos if they want them to work with PRs: <img width="485" alt="repo-config" src="https://user-images.githubusercontent.com/30140/38024621-7fe90278-327d-11e8-85b3-6f59a272aeba.png"> I originally raised this as an issue against the REST API - but it turns out there isn't a REST API I can see to configure the repository options and this issue affects repos created via the web UI too https://github.com/go-gitea/go-sdk/issues/100
GiteaMirror added the type/bugmodifies/api labels 2025-11-02 04:10:21 -06:00
GiteaMirror commented 2025-11-02 04:10:21 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 28, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 28, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 04:10:22 -06:00
Author
Owner
Copy Link

@adelowo commented on GitHub (Jan 28, 2019):

This is enabled by default this days I believe

@adelowo commented on GitHub (Jan 28, 2019): This is enabled by default this days I believe
GiteaMirror commented 2025-11-02 04:10:22 -06:00
Author
Owner
Copy Link

@jstrachan commented on GitHub (Jan 28, 2019):

@adelowo ah awesome thanks!

@jstrachan commented on GitHub (Jan 28, 2019): @adelowo ah awesome thanks!
GiteaMirror commented 2025-11-02 04:10:22 -06:00
Author
Owner
Copy Link

@apricote commented on GitHub (Jan 28, 2019):

For reference, all merge styles are enabled for new repos here https://github.com/go-gitea/gitea/blob/master/models/repo.go#L1311

@apricote commented on GitHub (Jan 28, 2019): For reference, all merge styles are enabled for new repos here https://github.com/go-gitea/gitea/blob/master/models/repo.go#L1311
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label modifies/api type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1707
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?