Open erochest opened 7 years ago
This is…a good issue. Poor travis was screaming into the void.
It also made the deployments fail (without actually failing).
Does feature/capistrano need to be maintained on its branch for deployment reasons? Or shall I work to merge it into master in the future?
Let's keep it in it's own branch. That way the extra files don't clutter master, which can act as a working branch. Then whenever we're ready to deploy, we merge master into feature/capistrano.
This happens on branch
feature/capistrano
.