You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is currently a heroku-status hubot script at https://github.com/github/hubot-scripts/blob/master/src/scripts/heroku-status.coffee . However, if my understanding of how the hubot eco-system has changed is correct, additional pull requests into hubot-scripts is no longer the preferred method. I think pulling that same functionality into this script would make sense, especially for verifying if Heroku is functioning correctly. It would not need any of the API auth, as the status endpoint is public.
I would be more than willing to submit a PR for this, but I wanted to see if you felt this project could use that functionality before I forked and added the code!
The text was updated successfully, but these errors were encountered:
Awesome, thanks! I'm working on a PR for this and have a request out to Heroku for some more documentation on what failure response JSON looks like, just so the tests can be more accurate.
There is currently a
heroku-status
hubot script at https://github.com/github/hubot-scripts/blob/master/src/scripts/heroku-status.coffee . However, if my understanding of how the hubot eco-system has changed is correct, additional pull requests into hubot-scripts is no longer the preferred method. I think pulling that same functionality into this script would make sense, especially for verifying if Heroku is functioning correctly. It would not need any of the API auth, as the status endpoint is public.I would be more than willing to submit a PR for this, but I wanted to see if you felt this project could use that functionality before I forked and added the code!
The text was updated successfully, but these errors were encountered: