Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a [commit status](https://help.github.com/articles/about-statuses/) is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the [`greenkeeper/initial`](https://github.com/captbaritone/redux-dropbox-middleware/commits/greenkeeper/initial) branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `greenkeeper/`.

We recommend using [Travis CI](https://travis-ci.org), but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the `greenkeeper/initial` branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s __settings__ page, under __Installed GitHub Apps__.

Start by checking whether a commit status is reported on the greenkeeper/initial branch and review the repository's CI configuration for newly created branches. Done means CI reports a status there, the greenkeeper/initial branch is deleted, and Greenkeeper is removed and re-added through the GitHub Apps allowlist so its initial pull request can be retriggered.

Written by the indexing model from the issue text.