πŸŽ„ Giving back little gifts of code for Christmas
Ruby HTML CSS JavaScript CoffeeScript Smarty Shell
Permalink
Failed to load latest commit information.
ansible Ruby 2.4.0 Dec 25, 2016
app Persist year param through infinite pagination links Jan 10, 2017
bin Add Docker development environment Jan 3, 2017
config Fix finished partial Jan 4, 2017
db Allow admin users to set a homepage on projects Dec 11, 2016
design remove codewall from assests Dec 8, 2016
lib Remove archived pull request related code Dec 15, 2016
public Make humans.txt dynamic (Issue #658) Nov 25, 2014
script Rake task to move archived prs to prs Dec 15, 2016
spec Fix finished partial Jan 4, 2017
test/mailers/previews Added preview for daily email Dec 10, 2014
vendor/assets/javascripts remove codewall from assests Dec 8, 2016
.codeclimate.yml First pass at replacing haml templates with erb using herbalizer #1568 Nov 7, 2016
.csslintrc Update codeclimate config Nov 4, 2016
.editorconfig Add .editorconfig http://editorconfig.org/ Dec 1, 2014
.eslintignore Update codeclimate config Nov 4, 2016
.eslintrc Update codeclimate config Nov 4, 2016
.gitignore Ignore ansible-galaxy playbook in .gitignore Nov 22, 2016
.pullreview.yml Add PullReview configuration file and enable JS review Nov 14, 2014
.rspec Format spec output as a christmas tree Dec 10, 2015
.rubocop.yml First pass at replacing haml templates with erb using herbalizer #1568 Nov 7, 2016
.ruby-version Ruby 2.4.0 Dec 25, 2016
.slugignore Added .slugignore to reduce slug size on heroku Nov 12, 2014
.travis.yml Ruby 2.4.0 Dec 25, 2016
CODE_OF_CONDUCT.md Updated contributor covenant to 1.4 Apr 1, 2016
CONTRIBUTING.md Update CONTRIBUTING.md to improve flow Dec 5, 2016
Dockerfile Bump ruby version to 2.4.0 on Dockerfile Jan 19, 2017
Gemfile Gem updates, fixes #1761, fixes #1762 Jan 13, 2017
Gemfile.lock Update dependencies, fixes #1818 Feb 18, 2017
LICENSE Updated copyright year May 2, 2016
Procfile Switched webserver from unicorn to puma on heroku Jan 26, 2015
Rakefile Rails-ify Nov 15, 2012
Readme.md Ruby 2.4.0 Dec 25, 2016
Vagrantfile Use RVM ansible-galaxy playbook, fixes #1596 Nov 22, 2016
coffeelint.json Update codeclimate config Nov 4, 2016
config.ru Fixed some rubocop warnings Dec 13, 2015
docker-compose.yml Add Docker development environment Jan 3, 2017

Readme.md

24 Pull Requests

Build Status Dependency Status Gitter chat Code Climate Test Coverage

Giving back little gifts of code 🎁

24 Pull Requests is a yearly initiative to encourage developers around the world to send 24 pull requests between December 1st and December 24th.

This is the site to help promote the project, highlighting why, how and where to send your pull requests.

Get started

Contributors

Over 180 different people have contributed to the project, you can see them all here: https://github.com/24pullrequests/24pullrequests/graphs/contributors

Development

Source hosted at GitHub. Report issues/feature requests on GitHub Issues. Follow us on Twitter @24pullrequests. We also hangout on Gitter.

Getting Started

New to Ruby? No worries! You can follow these instructions to install a local server, or you can use the included Vagrant setup.

Installing a Local Server

First things first, you'll need to install Ruby 2.4.0. I recommend using the excellent rbenv, and ruby-build

rbenv install 2.4.0
rbenv global 2.4.0

Next, you'll need to make sure that you have PostgreSQL installed. This can be done easily on OSX using Homebrew or by using http://postgresapp.com. Please see these further instructions for installing Postgres via Homebrew.

brew install postgres phantomjs

On Debian-based Linux distributions you can use apt-get to install Postgres:

sudo apt-get install postgresql postgresql-contrib libpq-dev

On Windows, you can use the Chocolatey package manager to install Postgres:

choco install postgresql

Now, let's install the gems from the Gemfile ("Gems" are synonymous with libraries in other languages).

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

If you are working on anything related to the email-generation code, you can use MailCatcher. Since we use Bundler, please read the following before using MailCatcher.

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

Using Vagrant

The included Vagrant setup uses Ansible as provisioner. First, you'll need to install the dependencies:

Windows Users: Ansible does not support Windows as controller machine, but there's a little hack in the Vagrantfile that will allow you to run the provision using a local SSH connection Guest-Guest. Just install Vagrant and VirtualBox, and you should be able to get it running.

Once you have everything installed, go to the project directory via console and run:

$ vagrant up

The first time you run vagrant up, the process will take several minutes, since it will download a box and run all necessary tasks to get the server ready. When the process is finished, log in to run the rails dev server:

$ vagrant ssh
$ cd /vagrant
$ bundle exec rails s -b 0.0.0.0

Then you should be able to access the application through your regular browser at http://192.168.12.34:3000.

Simply edit the files in the project directory using your favorite editor on your host machine and the changes will be automatically reflected in the /vagrant directory inside the guest virtual machine and so you can see the changes on your browser.

Tests

Standard RSpec/Capybara tests are used for testing the application. The tests can be run with bundle exec rake.

You can set up the test environment with bundle exec rake db:test:prepare, which will create the test DB and populate its schema automatically. You don't need to do this for every test run, but it will let you easily keep up with migrations. If you find a large number of tests are failing you should probably run this.

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.

Environment variables

bundle exec figaro install

Or for more information about using figaro, see https://github.com/laserlemon/figaro

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.

Code of Conduct

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.

Copyright

Copyright (c) 2016 Andrew Nesbitt. See LICENSE for details.