Lifestream

Results for #ci

09:43 utc aug 12 2019 permalink

Reported a build issue on #mruby with gperf 3.1 #ci #build #patch #github #artichoke https://github.com/mruby/mruby/issues/4628

07:13 utc may 24 2019 permalink

Adding #ci to a project is encouraging such better code hygiene. Because I want to make sure the build stays green, I actually make PRs even if it is only me approving them. Seeing the code in the browser makes it easier to review than #git diff #win

07:10 utc may 24 2019 permalink

In a related note, I now peg the nightly version in the rust-toolchain file to a specific date archive #ci #rust #win

07:09 utc may 24 2019 permalink

My #ci builds of ferrocarril caught a bug in rustyline that made compilation fail on the latest nightly #rust #win #patch https://github.com/kkawakam/rustyline/issues/217

01:23 utc may 17 2019 permalink

You can tell which parts of ferrocarril are new to me based on how many consecutive commits are dedicated to a feature. By this measure, the new (and hard) things were sys crates, #ci, and TryFrom traits #rust #win #fail

01:21 utc may 17 2019 permalink

I tried to explain continuous integration to my Dad and he synthesized it as "spellcheck for code" which is pretty good tbh #win #ci

08:47 utc may 16 2019 permalink

It only took 49 build jobs, but the ferrocarril build is passing on CircleCI https://circleci.com/gh/lopopolo/ferrocarril/47 This is the first time I've ever set up #ci for a side project #win