lukebatchelor

> $CHUNK is evaluated to "" outside of the bolt process, so we just see "" Ah yea, I was thinking about tools with a config.js which would mean bolt...

Changed files since master would look more like ``` git diff $(git merge-base master HEAD) --name-only ``` Which is equivalent to ``` git diff master...HEAD # possibly `git diff $(git...

Not sure what you mean @thejameskyle ? Are you referring to the first point? I think that ones still up for discussion. The second is just a product of requirements...

For reference [Failing build](https://bitbucket.org/atlassian/atlaskit-mk-2/addon/pipelines/home#!/results/26097)

Hey @Offirmo , @ahmedelgabri Sorry about the delay there. It's a good question for sure. There isn't anyone actively working on improving bolt day to day right now. Specific pieces...

By default bolt doesn't have any opinions on versioning, independent or otherwise. The publish command will just publish anything that has been bumped locally that is not on npm. Externally...

Hmm... That should work exactly the same as yarn, the installation is still handled completely by yarn, so resolutions should behave identically. Can you confirm if you're seeing the same...

Hi Phil, I replied above. Bolt doesn't do anything special with installation. It will resolve in exactly the same way as yarn, the only difference is that it symlinks at...

Would we attempt to parse the test block there, or allow it to run in the shell? Any idea how we could read the return code of that with passing...

Sweet. Just so I understand the idea here is to only link files that aren't already there essentially? One other thing we could consider, we currently symlink *all* root bin...