GitHub PushEvent at 2014-10-09 08:14:19
Repository: spree
Actor: peterberkenbosch
Payload: {"shas":[["ecdb8bcf94a1508d2ea774da57e1aaa0758acf05","4f54b115cfe4f019d6eed60b67e165e7f272f4bd@gmail.com","Moving admin index route to bottom of routes file to allow it to be overridden without breaking pagination on the orders page\n\nFixes #5461","Patrick Sinclair",true],["d94dd7509611c9a3e6ad5273b60140f3c0126c37","78d36d9f51a1dbe6b88f6b01fc521895038bd8de@gmail.com","Update jquery-ui-rails\n\nFixes #5462","Yann Marquet",true],["0f146c65c1385874b164a1cab7cbbd685bcb9f02","7473d776f167d8063ee875d8d5bc79aa17dd1b79@gmail.com","Add ability to track admin order canceler.\n\nFixes #5464","HoyaBoya",true],["c0fa14c78aca5aba9270d335673c565d4b741113","1e61407af37e8f6a3a550516842943c5d7d87094@brgh.net","Refactor some ReimbursementTypeEngine code\n\nNo behavior change.\nExtract a method to make it easier for subclasses to modify behavior by overriding just the \"calculate_reimbursement_type\" method.\nFixes #5465","Jordan Brough",true],["66446eaa8b5726690c3a6933a354be9650660fa2","5fce3282b80a9100dcff391e9ea6819c69565198@gmail.com","Remove 'disabled' from inputs in payments\n\nWith the Aug 27 commit, a601035bd199a49f7f74ccf04ed0d889ca895f3e, the inputs under `.payment-method` are being disabled on line 15 but never correctly undisabled. This fixes that issue. Looks like it is affecting most branches.\nfixes #5467","Eric Saupe",true],["0a3c0eb8a0d021fa84c51bd802c286df1d8afe09","10c3449ae54ae753f354dbeec60400de0a22a2ce@gmail.com","fix handling of credit cards expiring in current month\nfixes #5468","Paul Damer",true],["d20f7fd4f420ed44a5a7f9419552da832ad67346","a1a2cafa0fdb38c0c1ba9a8684bc380a939751b5@BurlingtonWebApps.com","Add Heroku deploy button.","Jeff Dutil",true],["5e8b564f98f42568545b4a9cd6047ddc04ea2ebf","a1a2cafa0fdb38c0c1ba9a8684bc380a939751b5@BurlingtonWebApps.com","Update app.json","Jeff Dutil",true],["9ab34b33d0dba05ef1e970c38ef63ec00f7639cc","a1a2cafa0fdb38c0c1ba9a8684bc380a939751b5@BurlingtonWebApps.com","Add buildpack url.","Jeff Dutil",true],["b68a5d5e93033bbda3b45654721e145a851dcd82","a1a2cafa0fdb38c0c1ba9a8684bc380a939751b5@BurlingtonWebApps.com","Remove deploy to heroku button. Fixes #5401","Jeff Dutil",true],["77dbfbdad3ad5d1234277ce18c6c0a3ea95defd9","a1a2cafa0fdb38c0c1ba9a8684bc380a939751b5@BurlingtonWebApps.com","Add issuestats badges.","Jeff Dutil",true],["48669ed26f9ae7e1f07a31f19fbce794ce44ef9c","5e1c0d6f8a0b550386d5f8342017b9898399fe26@gmail.com","Add Spree instrumentation\n\nAdd instrumentation to some checkout methods\n\nFixes #4802","John Hawthorn",true],["ecd181bf836a5a7e6cd72fd6c2449b4619451402","1e61407af37e8f6a3a550516842943c5d7d87094@brgh.net","Make best-promotion query more deterministic\n\nMostly for the benefit of the specs under MySQL.\n\nThis query was generating some sporadic spec failures for me when using MySQL as the database. This is because MySQL does not store fractional seconds so the \"created_at\" was sometimes the same value for two adjustments when running specs. And when created_at is identical the query below would actually pick the earlier adjustment instead of the more recent one.  Adding \"id\" as a fallback ordering fixes this problem and makes the behavior more deterministic.\n\nThe issue is reproduceable in postgres as well by using Timecop.\n\nFixes #4943","Jordan Brough",true],["a9c1f7d9c715c3b50a97b311826bb453b0b63d5b","9360ad07b634e0457b94b7332be0bf991d210927@vinsol.com","fix spelling for interim in image model--skip-ci\nfixes #5469","abhishek",true]],"size":14,"ref":"refs/heads/master","head":"a9c1f7d9c715c3b50a97b311826bb453b0b63d5b"}