<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"><br></div><div dir="ltr"><br>On Jan 2, 2019, at 8:13 AM, Nicolas Cellier <<a href="mailto:nicolas.cellier.aka.nice@gmail.com">nicolas.cellier.aka.nice@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><span></span></div></blockquote><blockquote type="cite"><div dir="ltr"><div dir="auto">Reminder: we also have [skip travis] and [skip appveyor] when we only change platforms specific files, or build instructions.</div></div></blockquote><div><br></div>IMO this info should be in CONTRIBUTING.md alongside the description of <span style="background-color: rgba(255, 255, 255, 0);">[skip ci]. I never knew about this. I never knew about [skip ci]. Don’t assume users are familiar with script intervals, or github fundamentals, or whatever other mechanism implements the [skip *] facility. Best to document it in the right place.</span><div><br></div><div>Also <span style="background-color: rgba(255, 255, 255, 0);">CONTRIBUTING.md should start with a table of contents. It is nearly tl;dr</span></div><div><br><blockquote type="cite"><div dir="ltr"><br><div class="gmail_quote"><div dir="ltr">Le mer. 2 janv. 2019 à 16:15, Fabio Niephaus <<a href="mailto:lists@fniephaus.com">lists@fniephaus.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div><br></div><div><br><div class="gmail_quote"><div dir="ltr">On Wed, 2 Jan 2019 at 3:46 pm, Nicolas Cellier <<a href="mailto:nicolas.cellier.aka.nice@gmail.com" target="_blank" rel="noreferrer">nicolas.cellier.aka.nice@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div dir="ltr">Or maybe we don't interrupt jobs that already started?</div></blockquote><div dir="auto"><br></div><div dir="auto">I think you are right. If that's not the case, we should fix it. Also, we should use [ci skip] more often (but carefully of course).</div><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr">Le mer. 2 janv. 2019 à 15:44, Nicolas Cellier <<a href="mailto:nicolas.cellier.aka.nice@gmail.com" target="_blank" rel="noreferrer">nicolas.cellier.aka.nice@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div>Hi all,</div><div>didn't we configure appveyor to cancel the builds when a newer commit is performed in the same branch/PR?</div><div><br></div><div>Currently, job queue is too deep (and slow)<br></div><div><a href="https://ci.appveyor.com/project/OpenSmalltalk/vm/history" target="_blank" rel="noreferrer">https://ci.appveyor.com/project/OpenSmalltalk/vm/history</a><br></div></div></div>
</blockquote></div>
</blockquote></div></div>
</blockquote></div>
</div></blockquote></div></body></html>