With certain data in the committer's name, for instance, we get a Encoding::InvalidByteSequenceError for US-ASCII.
Link to customize notifications now points directly to the notifications docs. [ci skip]
Add find_requests service and requests API data
422 is returned when the commit status can't be found anymore, 401 when the credentials are invalid.
This raises a needless error. The proper check seems unaffected by this piece of code, as it's handled in the Request::Branches class.
This is an unrecoverable error. Ideally, at some point, we have notifications in place to let people know. For now, this error shouldn't bubble up.
These can happen when we can't decrypt the credentials properly, including garbage in the URL, causing this unrecoverable errror.
They don't need to be reraised as the URI is unlikely to become valid at a later point.
db: remove unused and rarely used indices
This causes the stubs not to get torn down after the test, and they can resurface again at a later point, leading to some interesting test failures.
allow per-channel key to be specified for IRC notifications
Update README and add READMEs in sub-directories
At the moment we don't do a great job when it comes to communicating what's going on under the hood when you push a build to github - it either shows on the builds list or not. In the latter case users may be left in the dark, which I suspect may be more common in the future, when we move such things like "exclude branch" to the repository settings pane. This commit reveals part of the request data, which we can use to show what did we get from github and if it was accepted.
This index can be useful when debugging, otherwise one would have to do this via builds.
…late Add a repository_short_name value to the template
Deprecate repository in favor of repository_slug