@ -71,23 +71,21 @@ to make sure your changes don't cause regression elsewhere.
Here's how to run the test suite:
Here's how to run the test suite:
- Install the correct version of the drone-cli package. As of this
- code lint
writing, the correct drone-cli version is
[1.2.0 ](https://docs.drone.io/cli/install/ ).
| | |
- Ensure you have enough free disk space. You will need at least
| :-------------------- | :---------------------------------------------------------------- |
15-20 Gb of free disk space to hold all of the containers drone
|``make lint`` | lint everything (not suggest if you only change one type code) |
creates (a default AWS or GCE disk size won't work -- see
|``make lint-frontend`` | lint frontend files |
[#6243 ](https://github.com/go-gitea/gitea/issues/6243 )).
|``make lint-backend`` | lint backend files |
- Change into the base directory of your copy of the gitea repository,
and run `drone exec --event pull_request` .
- run test code (Suggest run in linux)
- At the moment `drone exec` doesn't support the Docker Toolbox on Windows 10
(see [drone-cli#135 ](https://github.com/drone/drone-cli/issues/135 ))
| | |
| :------------------------------------- | :----------------------------------------------- |
The drone version, command line, and disk requirements do change over
|``make test[\#TestSpecificName]`` | run unit test |
time (see [#4053 ](https://github.com/go-gitea/gitea/issues/4053 ) and
|``make test-sqlite[\#TestSpecificName]``| run [integration ](integrations ) test for sqlite |
[#6243 ](https://github.com/go-gitea/gitea/issues/6243 )); if you
|[More detail message about integrations](integrations/README.md) |
discover any issues, please feel free to send us a pull request to
update these instructions.
## Vendoring
## Vendoring