{"push_id":567528462,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"84f557d2df161eed4e8cf6639982b1981930a615","before":"741d452fc69d5295445f235e45615073f6a5a858","commits":[{"sha":"84f557d2df161eed4e8cf6639982b1981930a615","author":{"email":"5dcddd8c35fdf6eb881ea4df21e8a28d2947c291@thoughtbot.com","name":"Jon Yurek"},"message":"Add a semicolon to the PATH definition\n\nSo, this seems trivial, but according to #77, the previous behavior\ncaused a problem with more complicated commands. Granted, it seems weird\nto call commands like `if [thing]; then true; else false; fi` but here\nwe are. If I add the semicolon, then the shell treats it as a separate\ncommand. This means it modifies the shell env, but this is fine in the\nsubshell environment we're running the command in. Normally, if you were\nrunning this on your command line, I wouldn't recommend it: as I said,\nthis would modify your environment instead of modifying the command's\nenvironment. But we should be good here.","distinct":true,"url":"https://api.github.com/repos/thoughtbot/cocaine/commits/84f557d2df161eed4e8cf6639982b1981930a615"}]}