[Feature request] Pull requests: Test for code quality #3080

New Issue

GiteaMirror · 2025-11-02T05:00:13-06:00

GiteaMirror commented

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

Originally created by @3l73 on GitHub (Mar 20, 2019).

During pull request the developer is able to check the code of the given changes.

Next to this kind of manually check it should be possible to configure additional automatic tests like linter or code sniffer.

These kind of tests could be registered globally und configured locally inside the repository/project.

A test could be executed on the local machine where the gitea service is located or remote by an REST-Request.

Inside the repository/project the owner could configure following behaviour

the tests are deactivated (default)
negative results treated as warnings
negative results treated as errors and make a merge impossible until the issues are solved

The owner can exclude specific files or file patterns to be excluded from the test.

After the developer created a pull request or pushes changes inside an existing one, a timer starts to trigger the tests suits.

Originally created by @3l73 on GitHub (Mar 20, 2019). During pull request the developer is able to check the code of the given changes. Next to this kind of manually check it should be possible to configure additional automatic tests like linter or code sniffer. These kind of tests could be registered globally und configured locally inside the repository/project. A test could be executed on the local machine where the gitea service is located or remote by an REST-Request. Inside the repository/project the owner could configure following behaviour - the tests are deactivated (default) - negative results treated as warnings - negative results treated as errors and make a merge impossible until the issues are solved The owner can exclude specific files or file patterns to be excluded from the test. After the developer created a pull request or pushes changes inside an existing one, a timer starts to trigger the tests suits.

GiteaMirror added the type/proposal label 2025-11-02 05:00:13 -06:00

GiteaMirror closed this issue

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

GiteaMirror commented

2025-11-02 05:00:14 -06:00

@jonasfranz commented on GitHub (Mar 20, 2019):

That's already possible by using a CI like drone. There is in my opinion no need to run the linter on gitea itself.

@jonasfranz commented on GitHub (Mar 20, 2019): That's already possible by using a CI like drone. There is in my opinion no need to run the linter on gitea itself.

GiteaMirror commented

2025-11-02 05:00:14 -06:00

@3l73 commented on GitHub (Mar 20, 2019):

Question is, if there is the possibility to use the result in order to make a Pull request blocked until all issues are solved.

This request was not intended to integrate sniffer or linter itself in gitea, it is more in direction to integrate the service inside of a pull request.

@3l73 commented on GitHub (Mar 20, 2019): Question is, if there is the possibility to use the result in order to make a Pull request blocked until all issues are solved. This request was not intended to integrate sniffer or linter itself in gitea, it is more in direction to integrate the service inside of a pull request.

GiteaMirror commented

2025-11-02 05:00:14 -06:00

@markusamshove commented on GitHub (Mar 20, 2019):

Then it is a duplicate of #3588 :-)

@markusamshove commented on GitHub (Mar 20, 2019): Then it is a duplicate of #3588 :-)

GiteaMirror commented

2025-11-02 05:00:14 -06:00

@markusamshove commented on GitHub (Mar 20, 2019):

Or #996 both kind of go into the same direction

@markusamshove commented on GitHub (Mar 20, 2019): Or #996 both kind of go into the same direction

GiteaMirror commented

2025-11-02 05:00:15 -06:00