Joe Corcoran 77dcdaa482 Use travis-settings to manage JSON settings field ... Since we use repository.settings as a kind of dump for all sorts of settings, some user-facing and some not, this lets us leave the db as it is, but pretend to have separate models for each "kind" of setting.		2016-07-01 23:55:49 -04:00
..
app	Add enable_for_all? condition	2016-06-28 11:35:47 -07:00
enqueue/services	Remove 'type' from payload	2016-06-15 14:36:59 +02:00
serialize	move tracking github oauth scopes out of the user model, and into Travis::Github::Oauth	2016-06-19 17:33:03 +02:00
v3	Use travis-settings to manage JSON settings field	2016-07-01 23:55:49 -04:00
workers	Check for repository owner instead of current user to validate feature flag	2016-06-23 15:15:31 -05:00
app.rb	get rid of spec_helper_core	2016-06-19 14:35:54 +02:00
attack.rb	no longer test against user agent for github rate-limit, since it is not consistently github-camo	2016-07-01 16:27:41 +02:00
instruments.rb	only run Skylight for 20% of the dynos (rounding up if there are less than five)	2015-01-19 14:00:00 +01:00
serialize.rb	move travis/api/serialize/* from core to lib	2016-06-18 18:01:09 +02:00
v3.rb	add specs, update error names	2016-04-20 14:31:08 +02:00