mirror of
https://github.com/teamcapybara/capybara.git
synced 2022-11-09 12:08:07 -05:00
Make it clearer that general problems should go to the mailing list, not the issue tracker
This commit is contained in:
parent
c3f2c44eee
commit
e1091daced
1 changed files with 5 additions and 5 deletions
10
README.rdoc
10
README.rdoc
|
@ -26,12 +26,12 @@ On OSX you may have to install libffi, you can install it via MacPorts with:
|
||||||
== Development:
|
== Development:
|
||||||
|
|
||||||
* Source hosted at {GitHub}[http://github.com/jnicklas/capybara].
|
* Source hosted at {GitHub}[http://github.com/jnicklas/capybara].
|
||||||
* Please direct questions, discussions at the {mailing list}[http://groups.google.com/group/ruby-capybara].
|
* Please direct questions, discussion or problems to the {mailing list}[http://groups.google.com/group/ruby-capybara].
|
||||||
* Report issues on {GitHub Issues}[http://github.com/jnicklas/capybara/issues]
|
* If you found a reproducible bug, open a {GitHub Issue}[http://github.com/jnicklas/capybara/issues] to submit a bug report.
|
||||||
|
|
||||||
Pull requests are very welcome! Make sure your patches are well tested, Capybara is
|
Pull requests are very welcome (and even better than bug reports)! Make sure
|
||||||
a testing tool after all. Please create a topic branch for every separate change
|
your patches are well tested, Capybara is a testing tool after all. Please
|
||||||
you make.
|
create a topic branch for every separate change you make.
|
||||||
|
|
||||||
Capybara uses bundler in development. To set up a development environment, simply do:
|
Capybara uses bundler in development. To set up a development environment, simply do:
|
||||||
|
|
||||||
|
|
Loading…
Add table
Reference in a new issue