MarcoBuster/gitea
1
0
Fork 0
mirror of https://github.com/go-gitea/gitea synced 2024-11-16 18:19:27 +01:00
Code Issues Packages Projects Releases Wiki Activity

docs: update 'Testing redux' in CONTRIBUTING.md (#11386)

Browse Source 
* docs: update 'Testing redux' in CONTRIBUTING.md

try simplfy it to make it more easy for contributor to follow it to
test their work by themselves.

Signed-off-by: a1012112796 <1012112796@qq.com>

* align help message strings

Co-authored-by: techknowlogick <techknowlogick@gitea.io>
This commit is contained in:
赵智超 2020-05-15 07:28:26 +08:00 committed by GitHub
parent 66a9ef9036
commit 4159866528
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 37 additions and 39 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
CONTRIBUTING.md
View File

@ -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
creates (a default AWS or GCE disk size won't work -- see
[#6243](https://github.com/go-gitea/gitea/issues/6243)).
- Change into the base directory of your copy of the gitea repository,
and run `drone exec --event pull_request`.
- 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 | | |
time (see [#4053](https://github.com/go-gitea/gitea/issues/4053) and | :-------------------- | :---------------------------------------------------------------- |
[#6243](https://github.com/go-gitea/gitea/issues/6243)); if you |``make lint`` | lint everything (not suggest if you only change one type code) |
discover any issues, please feel free to send us a pull request to |``make lint-frontend`` | lint frontend files |
update these instructions. |``make lint-backend`` | lint backend files |
- run test code (Suggest run in linux)
| | |
| :------------------------------------- | :----------------------------------------------- |
|``make test[\#TestSpecificName]`` | run unit test |
|``make test-sqlite[\#TestSpecificName]``| run [integration](integrations) test for sqlite |
|[More detail message about integrations](integrations/README.md) |
## Vendoring ## Vendoring

4
Makefile
View File

@ -164,8 +164,8 @@ help:
@echo " - revive run revive linter" @echo " - revive run revive linter"
@echo " - misspell check for misspellings" @echo " - misspell check for misspellings"
@echo " - vet examines Go source code and reports suspicious constructs" @echo " - vet examines Go source code and reports suspicious constructs"
@echo " - test run unit test" @echo " - test[\#TestSpecificName] run unit test"
@echo " - test-sqlite run integration test for sqlite" @echo " - test-sqlite[\#TestSpecificName] run integration test for sqlite"
@echo " - pr#<index> build and start gitea from a PR with integration test data loaded" @echo " - pr#<index> build and start gitea from a PR with integration test data loaded"
.PHONY: go-check .PHONY: go-check