Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add section on continuous integration #6

Open
campoy opened this issue Jun 30, 2017 · 2 comments
Open

Add section on continuous integration #6

campoy opened this issue Jun 30, 2017 · 2 comments

Comments

@campoy
Copy link
Owner

campoy commented Jun 30, 2017

Currently this is pretty sad.

@campoy campoy added this to the 1.0 milestone Jun 30, 2017
@object88
Copy link

object88 commented Jul 2, 2017

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?

@campoy
Copy link
Owner Author

campoy commented Jul 5, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants