24 Pull Requests
“Giving back little gifts of code”
24 Pull Requests is a yearly initiative to encourage developers around the world to send a pull request every day in December up to Christmas.
This is the site to help promote the project, highlighting why, how and where to send your pull requests.
- Andrew Nesbitt
- Chris Lowder
- Baris Balic
New to Ruby? No worries!
rbenv install 2.0.0-p353 rbenv global 2.0.0-p353
brew install postgres phantomjs
Now, let's install the gems from the
Gemfile ("Gems" are synonymous with libraries in other
gem install bundler && rbenv rehash bundle install
Once all the gems are installed, we'll need to create the databases and tables. Rails makes this easy through the use of "Rake" tasks.
bundle exec rake db:create:all bundle exec rake db:migrate
And we can also add some sample data with the seed task
bundle exec rake db:seed
Almost there! Now all we have to do is start up the Rails server and point our browser to http://localhost:3000
bundle exec rails s
Standard RSpec/Capybara tests are used for testing the application. The
tests can be run with
bundle exec rake.
should be placed in
bundle exec rake konacha:serve.
If you are using the omniauth environment variables (GITHUB_KEY, GITHUB_SECRET, TWITTER_KEY, TWITTER_SECRET) for another project, you will need to either
- unset them before running your tests or
- reset the omniauth environment variables after creating a Github (omniauth) application for this project
as it will use it to learn more about the developers and for pull requests.
Note on Patches/Pull Requests
- Fork the project.
- Make your feature addition or bug fix.
- Add tests for it. This is important so I don't break it in a future version unintentionally.
- Send a pull request. Bonus points for topic branches.
Copyright (c) 2013 Andrew Nesbitt. See LICENSE for details.