ama

ama copied to clipboard

Since you create so many repos and have a .travis.yml in all of them, do you manually enable Travis Ci for each project or you have some automation in place?

He uses several boilerplate repositories.

• node-module-boilerplate (generator)
• gulp-plugin-boilerplate (generator)
• electron-boilerplate (generator)
• appveyor-node

I might have missed something, but the point is, he uses a starting boilerplate and/or generator to help start projects.

He also uses np, xo, and ava in most of his projects for a streamlined workflow.

That said, there a lot of modules he rarely updates simply because they rarely require a change. He said this himself, but I can't seem to find a source.

I see, but that's how he creates the project. But for each module created, does he manually open travis-ci.org, search the repo and enable it?

(I understand it's not a huge task. I am just curious since he has to do it so often.)

I'm not sure, guess I missed that bit. Travis-ci does have an API endpoint for that purpose.

Edit: Travis-ci links to their .com domain for documentation, but the same page does exist on their .org domain. They also have a ruby-gem for convenience.