How we approach CI/CD · Resend

find out if you’re really doing CI, ask your team the following questions: Are all the developers on the team checking into trunk (not just merging from trunk into their branches or working copies) at least once a day? In other words, are they doing trunk-based development and working in small batches? Does every change to trunk kick off a build pr

Without any sort of outside continuous integration (CI) tooling, you can use the gh-pages branch that GitHub provides for actual publishing. Using the gh-pages branch means that your workflow needs to include merging to gh-pages at specific times for publishing purposes.

The First Way enables fast left-to-right flow of work from Development to Operations to the customer. In order to maximize flow, we need to make work visible, reduce our batch sizes and intervals of work, build in quality by preventing defects from being passed to downstream work centers, and constantly optimize for the global goals.