Bertrand Marron

For readability of the table we should keep the names short, so if there is only one `message.json` we should keep it as is. Yeah, we should store the full...

We should also sort the table by path/name when this gets added. :) Today it looks like new found resources just get added to the array of resources and are...

Hmm, `/tmp/circle-artifacts.XXXXX/` seems pretty safe to strip, no? As long as they don’t change the names… Though, I wouldn’t mind specifying a specific artifact path to benefit from that feature....

Hi @Daniel15, following up on this… `$CIRCLE_ARTIFACTS` was only for CircleCI 1.0, right? With the following config ```yml - store_artifacts: name: Store built bundles for stats path: bundle-stats ``` I’m...

Agreed. We should definitely store the full path.

And on this PR https://github.com/etalab/geo.data.gouv.fr/pull/563, I opened the PR before the build finished, didn’t get a comment. Updated something and forced push, and now I have one.

Did the exact same thing on this PR: https://github.com/etalab/geo.data.gouv.fr/pull/566 never got a comment at all.

Ah yeah, you’re right about the first one. Sorry for the ultra large PR, I should have picked a smaller one to enable this on 😄. Unfortunately I’m not really...

Hey @davidbarratt, This wouldn’t be a bad idea. I don’t want this repo to hold too many features besides parsing though but this could be light enough. If you want...

What do you think about using the GitHub API, something like https://api.github.com/repos/sindresorhus/np/statuses/master and checking that everything is `successful`?