1. 15 2月, 2015 1 次提交
    • V
      Upgrade to Rails 4.1.9 · 76aad9b7
      Vinnie Okada 提交于
      Make the following changes to deal with new behavior in Rails 4.1.2:
      
      * Use nested resources to avoid slashes in arguments to path helpers.
      76aad9b7
  2. 13 2月, 2015 3 次提交
  3. 12 2月, 2015 2 次提交
  4. 03 2月, 2015 3 次提交
  5. 02 2月, 2015 2 次提交
  6. 29 1月, 2015 3 次提交
  7. 27 1月, 2015 2 次提交
  8. 24 1月, 2015 2 次提交
  9. 23 1月, 2015 1 次提交
  10. 21 1月, 2015 3 次提交
  11. 18 1月, 2015 1 次提交
  12. 30 12月, 2014 1 次提交
  13. 29 12月, 2014 2 次提交
  14. 24 12月, 2014 1 次提交
  15. 20 11月, 2014 2 次提交
    • D
      HipChat service: support custom servers · 1353f9aa
      Daniel Aquino 提交于
      HipChat allows users to run their own private servers and to be able to
      support those we must connect to the correct URL when using one of these
      custom servers.
      1353f9aa
    • D
      HipChat service: correct service name & use v2 API · 2f3df4cb
      Doug Goldstein 提交于
      HipChat refers to their own product camel cased so we should do the
      same. HipChat no longer recommends people use the deprecated v1 API so
      switch to using the v2 API by default. hipchat-rb does not yet default
      to v2 in any version so it must be specified.
      2f3df4cb
  16. 06 11月, 2014 1 次提交
  17. 05 11月, 2014 1 次提交
  18. 29 10月, 2014 2 次提交
  19. 28 10月, 2014 1 次提交
  20. 24 10月, 2014 1 次提交
    • S
      update slack-notifier to 1.0.0, use raw webhook_url per slack recommendation · 7b339e61
      Steven Sloan 提交于
      per changes with slack, they’re now using “static” web hook urls that describe the team & service with IDs that don’t change if the team or service name change. their recommendation is to use the raw webhook_url instead of building it out of components to allow more flexibility
      
      this should also prevent issues cropping up with mistakes in how the urls are parsed
      7b339e61
  21. 21 10月, 2014 2 次提交
  22. 09 10月, 2014 1 次提交
  23. 08 10月, 2014 1 次提交
  24. 06 10月, 2014 1 次提交