If you want to contribute to GitLab, follow this process:
If you want to contribute to GitLab, follow this process:
...
@@ -7,24 +7,20 @@ If you want to contribute to GitLab, follow this process:
...
@@ -7,24 +7,20 @@ If you want to contribute to GitLab, follow this process:
3. Code
3. Code
4. Create a pull request
4. Create a pull request
We will only accept pull requests if:
We will only accept pull requests if:
* Your code has proper tests and all tests pass
* Your code has proper tests and all tests pass
* Your code can be merged w/o problems
* Your code can be merged w/o problems
* It won't break existing functionality
* It won't break existing functionality
* It's quality code
* It's quality code
* We like it :)
* We like it :)
## [You may need a developer VM](https://github.com/gitlabhq/developer-vm)
For examples of feedback on pull requests please look at the [closed pull requests](https://github.com/gitlabhq/gitlabhq/pulls?direction=desc&page=1&sort=created&state=closed).
## Running tests
## Installation
To run the specs for GitLab, you need to run seeds for test db.
cd gitlabhq
Install the Gitlab development in a virtual machine with the [Gitlab Vagrant virtual machine](https://github.com/gitlabhq/gitlab-vagrant-vm). Installing it in a virtual machine makes it much easier to set up all the dependencies for integration testing.
rake db:seed_fu RAILS_ENV=test
Then you can run the test suite with rake:
## Running tests
rake gitlab:test
For more information on running the tests please read the [development tips](https://github.com/gitlabhq/gitlabhq/blob/master/doc/development.md)
Install the Gitlab development in a virtual machine with the [Gitlab Vagrant virtual machine](https://github.com/gitlabhq/gitlab-vagrant-vm). Installing it in a virtual machine makes it much easier to set up all the dependencies for integration testing.