go-tooling-workshop
go-tooling-workshop copied to clipboard
Add section on continuous integration
I'm working on a tool for "local" CI stuff right now, so have been thinking about this. Are you interested in what happens on the dev desktop (some process watches for code changes, and automatically runs some process when changes are made), or strictly on 3rd party tools like Travis?
I'm thinking about continuous integration as a process run on pull requests before they get merged. Travis is a good example but there's many others.
For now I'd like to keep it as simple as possible, explaining why this is important, and giving example of the most common tools.