Bye, tachikoma gem
•
0 likes•1,415 views
The document discusses the deprecation of the "Tachikoma gem" and transition to continuing support for the "Tachikoma.io service" instead. It also references tools for checking code style and formatting like Saddler gem and Reviewdog, and submitting changes to GitHub. Additionally, it mentions Heroku changing their CLI tool from a Go implementation to Node.js to avoid issues with OS updates and cross-compiling.
Bye, tachikoma gem
- 1. Notice: “Tachikoma gem” is deprecated. We’ll continue “Tachikoma.io service”.
- 2. Bye, tachikoma gem id: sanemat (サネマツ), むらはし
- 3. The problem is... We should `bundle update` regularly, frequently. But … Tachikoma gem
- 4. 2013-05-31 - Kensuke Nagae #rubykaigi2013 @kyanny
- 5. “Continuous improvement is important. You may be able to do.” - Kensuke Nagae
- 6. ...I found the slide which I want to talk, at 2015-12-10?? :-/
- 7. Tachikoma gem first version v2.0.0 commit
- 9. 2014-09-17 - Kenichi Murahashi #Travis CI Meetup @sanemat Release announce about tachikoma.io
- 10. Why is “tachikoma gem” deprecated?
- 14. Notice: “Tachikoma gem” is deprecated. We’ll continue “Tachikoma.io service”.
- 15. Appendix: Saddler gem does not become a trend You should use reviewdog (golang)
- 16. The problem is... Run anything -> to -> GitHub. There are a lot of different tools.
- 17. Saddler gem Run anything -> to checkstyle format -> Saddler gem -> GitHub. Simple tool.
- 18. Reviewdog Run anything -> to checkstyle format -> Reviewdog -> GitHub. Simple tool.
- 20. Evolution of the Heroku CLI: 2008-2017 | Heroku HerokuがCLIツールをGo実装からPure Node.js実装に変更した話。 GoはOS更新の影響でネットワーク周りの問題が起きがちだったりク ロスコンパイルが辛かったとのこと b.hatena/teppeis