6 ms·

If you pass along your codebases today, all that is included?

• l0b0 6y ago
  Re-reads Yes. It is a bit of work, but not huge: - Use natural in-repo CI configuration like GitLab and Travis. That way a fork of the project can easily establish an identical pipeline. I can't imagine going back to Jenkins or the like at this point, where the CI pipeline is this massive snowflake waiting to break down, and always being out of sync with the code. - The current code base has 97% coverage which is verified by the CI pipeline. I'll reiterate the old trope about this making the development faster, in no small part because we can do fearless refactoring. - Linters and formatters check the style pre-commit (only changed files) and in CI (all files). - I run a script nightly to reset my dev env completely. It + some documented configuration is all a new dev needs to get started. - Keeping the documentation in the repo makes sure that every change is peer reviewed. That not only sets a minimum bar for the quality but also makes sure at least one other person has already read it once it's available to everyone.