Disallow merging until the CI bot reports about success build #1569

New Issue

GiteaMirror · 2025-11-02T04:05:16-06:00

GiteaMirror commented

2025-11-02 04:05:16 -06:00

Originally created by @iddm on GitHub (Feb 26, 2018).

This is supported for the github and travis CI, for example. So, using a github and travis CI you may configure it so that it is impossible to merge the pull requests before the CI bot allows you.

Originally created by @iddm on GitHub (Feb 26, 2018). This is supported for the github and travis CI, for example. So, using a github and travis CI you may configure it so that it is impossible to merge the pull requests before the CI bot allows you.

GiteaMirror added the issue/confirmed type/feature labels 2025-11-02 04:05:16 -06:00

GiteaMirror closed this issue

2025-11-02 04:05:16 -06:00

GiteaMirror commented

2025-11-02 04:05:17 -06:00

@iddm commented on GitHub (Oct 28, 2018):

Are there any estimations on this? Could we put a milestone on it? Do you guys have some discussions regarding issues, which goes where, for example? :)

@iddm commented on GitHub (Oct 28, 2018): Are there any estimations on this? Could we put a milestone on it? Do you guys have some discussions regarding issues, which goes where, for example? :)

GiteaMirror commented

2025-11-02 04:05:17 -06:00

@lunny commented on GitHub (Oct 29, 2018):

This should be an option on branch protected I think.

@lunny commented on GitHub (Oct 29, 2018): This should be an option on branch protected I think.

GiteaMirror commented

2025-11-02 04:05:17 -06:00

@stale[bot] commented on GitHub (Jan 5, 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 5, 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:05:17 -06:00

@NicolasPetton commented on GitHub (Jan 30, 2019):

Any update on this issue? I'd love to have something like this in gitea.

@NicolasPetton commented on GitHub (Jan 30, 2019): Any update on this issue? I'd love to have something like this in gitea.

GiteaMirror commented

2025-11-02 04:05:17 -06:00

@lafriks commented on GitHub (Jan 30, 2019):

@NicolasPetton noone is working on this currently

@lafriks commented on GitHub (Jan 30, 2019): @NicolasPetton noone is working on this currently

GiteaMirror commented

2025-11-02 04:05:18 -06:00

@japettyjohn commented on GitHub (Apr 25, 2019):

Besides the integration with the pull request process itself, the merge requirement seems it could be met by adding to the required approvals a list of users/teams required in combination with the existing "number of required approvals" currently implemented.

@japettyjohn commented on GitHub (Apr 25, 2019): Besides the integration with the pull request process itself, the merge requirement seems it could be met by adding to the required approvals a list of users/teams required in combination with the existing "number of required approvals" currently implemented.

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#1569