@@ -25,7 +25,6 @@ looking for a quick way to help out.
25
25
#### Pull Requests
26
26
27
27
- ** Make sure the test suite passes** on your box, Use the provided ` test_*.sh ` scripts or tox.
28
- - Enable [ Travis-Ci] ( http://travis-ci.org/pydata/pandas ) . See "Getting Travis-CI going" below.
29
28
- Use [ proper commit messages] ( http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html ) :
30
29
- a subject line with ` < 80 ` chars.
31
30
- One blank line.
@@ -71,47 +70,6 @@ looking for a quick way to help out.
71
70
72
71
https://groups.google.com/forum/#!topic/pystatsmodels/biNlCvJPNNY/discussion
73
72
74
- ### Getting Travis-CI going
75
-
76
- Instructions for getting Travis-CI installed are available [ here] ( http://about.travis-ci.org/docs/user/getting-started/ ) .
77
- For those users who are new to Travis-CI and [ continuous integration] ( https://en.wikipedia.org/wiki/Continuous_integration ) in particular,
78
- Here's a few high-level notes:
79
- - Travis-CI is a free service (with premium account upgrades available) that integrates
80
- well with GitHub.
81
- - Enabling Travis-CI on your GitHub fork of a project will cause any * new* commit
82
- pushed to the repo to trigger a full build+test on Travis-CI's servers.
83
- - All the configuration for Travis-CI builds is already specified by ` .travis.yml ` in the repo.
84
- That means all you have to do is enable Travis-CI once, and then just push commits
85
- and you'll get full testing across py2/3 with pandas' considerable
86
- [ test-suite] ( https://github.com/pydata/pandas/tree/master/pandas/tests ) .
87
- - Enabling Travis-CI will attach the test results (red/green) to the Pull-Request
88
- page for any PR you submit. For example:
89
-
90
- https://github.com/pydata/pandas/pull/2532 ,
91
-
92
- See the Green "Good to merge!" banner? that's it.
93
-
94
- It's important to get travis working as PRs won't generally get merged until travis is green.
95
-
96
- #### Steps to enable Travis-CI
97
-
98
- - Open https://travis-ci.org/
99
- - Select "Sign in with GitHub" (Top Navbar)
100
- - Select \[ your username\] -> "Accounts" (Top Navbar)
101
- - Select 'Sync now' to refresh the list of repos from your GH account.
102
- - Flip the switch for the repos you want Travis-CI enabled for.
103
- "pandas", obviously.
104
- - Then, pushing a * new* commit to a certain branch on that repo
105
- will trigger a build/test for that branch. For example, the branch
106
- might be ` master ` or ` PR1234_fix_everything__atomically ` , if that's the
107
- name of your PR branch.
108
-
109
- You can see the build history and current builds for your fork
110
- at: https://travis-ci.org/ (your_GH_username)/pandas.
111
-
112
- For example, the builds for the main pandas repo can be seen at:
113
- https://travis-ci.org/pydata/pandas .
114
-
115
73
####More developer docs
116
74
117
75
* See the [ developers] ( http://pandas.pydata.org/developers.html ) page on the
0 commit comments