🎄 Giving back little gifts of code
Switch branches/tags
Nothing to show
Clone or download
dependabot[bot] and andrew Bump i18n-tasks from 0.9.24 to 0.9.25 (#2323)
Bumps [i18n-tasks](https://github.com/glebm/i18n-tasks) from 0.9.24 to 0.9.25.
- [Release notes](https://github.com/glebm/i18n-tasks/releases)
- [Changelog](https://github.com/glebm/i18n-tasks/blob/master/CHANGES.md)
- [Commits](glebm/i18n-tasks@v0.9.24...v0.9.25)

Signed-off-by: dependabot[bot] <support@dependabot.com>
Latest commit 9897a14 Sep 18, 2018
Failed to load latest commit information.
ansible Ruby 2.5.1 Aug 27, 2018
app Suppress "Dangerous query method called with non-attribute argument" … Sep 5, 2018
bin Rails 5.2.1 Aug 27, 2018
config Rails 5.2.1 Aug 27, 2018
db Update schema Sep 12, 2018
design remove codewall from assests Dec 8, 2016
lib Use `update` instead of `update_attributes` Mar 4, 2018
public Fix map and map clusterer on about page (#2084) Nov 22, 2017
script Rake task to move archived prs to prs Dec 15, 2016
spec Fix spec Sep 12, 2018
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.5.1 Aug 27, 2018
.slugignore Added .slugignore to reduce slug size on heroku Nov 12, 2014
.travis.yml Ruby 2.5.1 Aug 27, 2018
CODE_OF_CONDUCT.md Update code of conduct Nov 30, 2017
CONTRIBUTING.md Update CONTRIBUTING.md to improve flow Dec 5, 2016
Dockerfile Ruby 2.5.1 Aug 27, 2018
Gemfile Bump pg from 1.1.2 to 1.1.3 Sep 7, 2018
Gemfile.lock Bump i18n-tasks from 0.9.24 to 0.9.25 (#2323) Sep 18, 2018
ISSUE_TEMPLATE.md Create Issue template (#2043) Oct 16, 2017
LICENSE Update copyright year Jan 2, 2018
Procfile Switched webserver from unicorn to puma on heroku Jan 26, 2015
Rakefile Rails-ify Nov 15, 2012
Readme.md Remove some broken readme badges (#2320) Sep 12, 2018
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


24 Pull Requests

Build Status Gitter chat

🎄 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.

Table of Contents

Get started


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


The source is hosted at GitHub. You can report issues/feature requests on GitHub Issues. Follow the project on Twitter @24pullrequests. People from this community also often hangout on Gitter.

These instructions are for working on the the 24pullrequests.com website. If you just want to be a developer who contributes PRs during the holidays, you don't need to follow these instructions! Go to https://24pullrequests.com and get involved there.

Getting Started

Want to hack on the website? Awesome!

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.5.1. I recommend using the excellent rbenv, and ruby-build.

rbenv install 2.5.1
rbenv global 2.5.1

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

Then you should be able to access the application through your regular browser at

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.


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


We are always looking for people to contribute! To find out how to help out, have a look at our Contributing Guide.

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 MIT © 2018 Andrew Nesbitt. See LICENSE for details.