Piotr Sarnacki edb4e19309 Run lastBuildDidChange only once for a runloop run ... When a lot of pusher events come with build updates, lastBuildDidChange can run quite frequently. We can avoid that by using scheduleOnce, which will ensure that only the last invocation of lastBuildDidChange will be run for a given runloop run.		2013-12-11 12:43:08 +01:00
..
account_index.coffee	Show all accounts and hooks in profile	2013-06-18 17:54:13 +02:00
accounts.coffee	Fix profile views	2013-02-21 23:22:53 +01:00
build.coffee	Pull some bindings into build and job controllers.	2013-09-08 10:11:20 +02:00
builds.coffee	show loading indicator on show-more button click	2013-07-27 16:11:12 -04:00
current_user.coffee	Delegate CurrentUserController#updateLocale to user instance	2013-09-01 14:22:48 +02:00
flash.coffee	Fix duplicated broadcasts	2013-12-04 16:20:16 +01:00
home.coffee	somewhat more consistent naming	2012-10-12 02:34:54 +02:00
job.coffee	Pull some bindings into build and job controllers.	2013-09-08 10:11:20 +02:00
profile.coffee	Reload hooks if they're not available	2013-09-16 18:53:13 +02:00
repo.coffee	Run lastBuildDidChange only once for a runloop run	2013-12-11 12:43:08 +01:00
repos.coffee	Fix problem with getting started template rendering on first sync	2013-10-29 20:48:27 +01:00
stats.coffee	Fix more specs	2013-03-04 03:46:04 +01:00