-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Use CircleCI as replacement of TravisCI #2720
Comments
I wanted to migrate over CircleCI for months! :) Let's do it as soon as possible. Feel free to move forward with this migration if you have some spare time. |
Let me know if you need any help, since this will affect #2743 aswell 🥳 |
I started the migration towards CircleCI. Feel free to contribute:) |
@kamilmysliwiec looking really nice - exactly how I had imagined it to be (with the mixins / aliases, etc. so awesome) :) The checks are so useful for a contributor: and the config is way cleaner and maintainable. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Just finished the migration of the main repo. I'll do the same for the rest of them too. If anyone wants to contribute, PRs are welcome! PS. @BrunnerLivio I think that @marcus-sa asked about NPM vs Yarn, not Yarn workspaces. I'm personally using NPM recently, but I don't have any preference here. Both aren't perfect, neither one convinced me, so I'm just using this one which is more popular now:) |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Feature Request
What is the motivation / use case for changing the behavior?
TravisCI is great for smaller projects and easy to get started with. In my opinion NestJS has grown out of this.
Some features why choose CircleCI over TravisCI:
Teachability, Documentation, Adoption, Migration Strategy
Migrate nestjs/nest to CircleCI. Migrate integrations only if needed.
The text was updated successfully, but these errors were encountered: