-
Notifications
You must be signed in to change notification settings - Fork 24
Commitlint does not work anymore #10
Comments
Hey @wzrdtales, thanks for opening this ✨ So sad to hear this 😞 again ( #9 ). I've two bots in my free Heroku plan: commitlint and DEP but both got popular recently and it seems the plan can't handle the load any longer. Both are forced sleep now :/ I can't afford a paid plan so If you would like to host your own instance of this app then this guide will help. Sorry for the inconvenience. Suggestions are welcome! |
Thanks for the information :) That helps! But still suggestions: Contact heroku, tell them what it is for and if they're willing to sponsor. Other alternatives, get money for the infrastructure through: Or some other alternative. For the latter ones you will depending on where you live require to comply to your local tax laws. I will setup my own instance now, so thank you for your response on this :) |
Ahh forgot openshift, they actually have a program for such stuff: |
@wzrdtales thanks for those suggestions. I will check them out. |
For some reason commitlint is not functioning anymore, just wanted to now first if I am the only one experiencing this?
See db-migrate/node-db-migrate#537 for reference, which is missing the commitlint output for an unknown reason. Have reinstalled the bot already to test if this would have been the source of the problem, but unfortunately it seems to be something different. Nothing was changed from the last time it worked though...
The text was updated successfully, but these errors were encountered: