Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

README.md: Add contributing/running tests section #197

Merged
merged 1 commit into from Feb 7, 2015

Conversation

msabramo
Copy link
Contributor

@msabramo msabramo commented Jan 4, 2015

with links to:

because I was looking for info on how to run tests in the main README.md and didn't find it and I only found about these other docs when @willdurand kindly pointed them out to me in #194 (comment)

@willdurand
Copy link
Contributor

Weird that the test suite fails for such a change..

👍 otherwise

@msabramo
Copy link
Contributor Author

msabramo commented Jan 5, 2015

Yeah, test failure looks spurious and unrelated to my change.

Can an admin please tell Travis to retest?

@dmp42
Copy link
Member

dmp42 commented Jan 5, 2015

Restarted. You should be able to trigger a rebuild by just git push -f it.

@dmp42
Copy link
Member

dmp42 commented Jan 5, 2015

LGTM otherwise! Nice to see interest in these.

@dmp42
Copy link
Member

dmp42 commented Jan 5, 2015

What about a CONTRIBUTING.md document where these (and other dev infos) would be put, instead of into the general README doc?

@willdurand
Copy link
Contributor

Agreed on a CONTRIBUTING file. Any template that you would like to use? I use this in most of my projects, and it should be easy to adapt it for this project.

@msabramo
Copy link
Contributor Author

msabramo commented Jan 5, 2015

OK, I moved the testing info from README.md to CONTRIBUTING.md (and put a link in README.md to CONTRIBUTING.md.

I'll leave it to someone more experienced to:

  • Document the canonical way to run the tests - I'm getting a lot of failures, so I'm not sure I'm doing stuff right.
  • Document what the standards are for coding, commit messages, etc.

@willdurand
Copy link
Contributor

To me, it is really important to add:

Here are a few rules to follow in order to ease code reviews, and discussions before maintainers accept and merge your work.

You MUST run the test suite.

You MUST write (or update) unit tests.

You SHOULD write documentation.

Please, write commit messages that make sense, and rebase your branch before submitting your Pull Request.

One may ask you to squash your commits too. This is used to "clean" your Pull Request before merging it (we don't want commits such as "fix tests", "fix 2", "fix 3", etc.).

Also, while creating your Pull Request on GitHub, you MUST write a description which gives the context and/or explains why you are creating it.

Thank you!

@dmp42
Copy link
Member

dmp42 commented Jan 7, 2015

+1 on @willdurand suggestion

with links to:

- [test/README.md](test/README.md)
- [test/functional/README.md](test/functional/README.md)

because I was looking for info on how to run tests in the main
`README.md` and didn't find it and I only found about these other docs
when @willdurand kindly pointed them out to me in
hipache#194 (comment)
@msabramo
Copy link
Contributor Author

msabramo commented Jan 7, 2015

@Starefossen
Copy link
Contributor

LGTM

@dmp42
Copy link
Member

dmp42 commented Feb 7, 2015

Merged then :)

dmp42 added a commit that referenced this pull request Feb 7, 2015
README.md: Add contributing/running tests section
@dmp42 dmp42 merged commit 2d36766 into hipache:master Feb 7, 2015
@willdurand
Copy link
Contributor

youpi!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants