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
My name is Andrey.
First of all, thank you. You've made a lot of work to create integration Capistrano with Slack. I enjoyed it very much on previous projects.
But in last few month project has not answered PR, outdated gems. It also does not support Capistrano 3 and new Slack API features and doesn't have tests.
So, do you have a plan to maintenance capistrano-slack and close above pointed bugs? If no, I'm ready to continue support and develop this gem because we use Capistrano and Slack in our projects actually.
The text was updated successfully, but these errors were encountered:
Hey guys, Sorry for the absence, i've kind of deprecated this project, as other solutions have emerged since, that solve this problem better than this project. This project was started right when slack came out as more of an internal band-aid. it is a fork of capistrano-mountaintop which was what we were already using for campfire when we swtiched. Our team has since moved all our projects to Capistrano-3, Mina or Ansible so there is really little motivation to continue development of the project. I invite people to find a replacement or fork the project and take it over, I wont be mad.
If you use capistrano 3, i highly recommend slackistrano, its what we use internally now with our Cap3 projects.
Hello, @j-mcnally.
My name is Andrey.
First of all, thank you. You've made a lot of work to create integration Capistrano with Slack. I enjoyed it very much on previous projects.
But in last few month project has not answered PR, outdated gems. It also does not support Capistrano 3 and new Slack API features and doesn't have tests.
So, do you have a plan to maintenance
capistrano-slack
and close above pointed bugs? If no, I'm ready to continue support and develop this gem because we use Capistrano and Slack in our projects actually.The text was updated successfully, but these errors were encountered: