Skip to content

add travis badge to GH page, imporve contributor guildelines #2774

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.

Sign up for GitHub

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

Merged
merged 2 commits into from Jan 30, 2013
Merged

add travis badge to GH page, imporve contributor guildelines #2774

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
23a2985
DOC: put contribution guidelines in CONTRIBUTING.md
Jan 30, 2013
cadc7a9
DOC: show travis build status on github page
Jan 30, 2013
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 35 additions & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1,35 @@
Please see [Developers](http://pandas.pydata.org/developers.html) page on the project website.
Guidelines
---

All contributions, bug reports, bug fixes, documentation improvments,
enhancements and ideas are welcome. Please try and follow these guidelines
as best you can, this makes it easier for us to accept your contribution or
address the issue you're having.

- When submitting a bug report:
- Please include a short, self-contained python snippet.
- Specify the pandas version used. (you can check `pandas.__version__`).
- Explain what the expected behavior was, and what you saw instead.
- When submitting a Pull Request
- **Make sure the test suite passes**., and that means on python3 as well.
You can use "test_fast.sh", or tox locally and/or enable Travis-CI on you're fork.
- We suggest you enable Travis-CI on your fork, to make it easier for the team
to see that the PR does indeed pass all the tests.
- Pandas cares about performance, you can use the included "test_perf.sh"
script to make sure your PR does not introduce any performance regressions
in the library.
- **Don't** merge upstream into a branch you're going to submit as a PR,
This can create all sorts of problems. Use "git rebase" instead. This ensures
no merge conflicts occur when you're code is merged by the core team.
- An informal commit message format is in use by the project, please try
and adhere to it. Use a "ENH: ", "TST:", "BUG:", "DOC:", etc' prefix in
your commit title. Check the output of "git log" for examples.
- doc/source/vx.y.z.txt contains an on-going change-log for the version under
development, look at previous versions, and add an entry as needed in
a separate commit in your PR.
- For extra brownie points, use "git rebase -i" to squash and reorder
commits in your PR so that the history makes the most sense. Use your own
judgment to decide what history needs to be preserved.

Please see [Developers](http://pandas.pydata.org/developers.html) page on
the project website for more details.
2 changes: 2 additions & 0 deletions README.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@
pandas: powerful Python data analysis toolkit
=============================================

.. image:: https://travis-ci.org/pydata/pandas.png

What is it
==========

Expand Down