This would be necessary so that if the resulting repo is connected to Travis CI then it will be tested. We would want it to run make test for us. We would also want it to run coveralls so that if coveralls is associated with Travis CI then the code coverage will be updated on that site.

If the new project is associated with Docker Hub then a Dockerfile is necessary to inform Dockerhub how to build the project.

Badges allow you to see the state of your project at any time without having to manually go to different locations.

Let's say you have the following setup:

• GitHub with your repository
• Travis CI linked to GitHub
• Coveralls linked to GitHub and Travis CI
• DockerHub linked to GitHub

The following would allow you to:

• On a push to github
• travis CI pulls down the changes and tests it
• It then notifies Coveralls with the coverage results
• Docker Hub also updates the public image that can be pulled down.

The badges would then show the following:

• Build Status (From Travis CI)
• Coverage Status (From Coverall)
• Docker Automated Build (From Docker Hub) - Whether its automated/manual/..