{"push_id":840392921,"size":1,"distinct_size":0,"ref":"refs/heads/master","head":"150d2d67ca743cd8f99db7f994d79fd2c5683673","before":"1c8edf0ec3d4141270233faa31110339c7827aff","commits":[{"sha":"150d2d67ca743cd8f99db7f994d79fd2c5683673","author":{"email":"8f9f97eb45ed102f8faf72e01bebf7b2c1679978@thoughtbot.com","name":"Calle Erlandsson"},"message":"Prefer `--force-with-lease` over `--force`\n\nUsing `--force-with-lease` allows one to force push without the risk of\nunintentionally overwriting someone else's work.\n\nThe git-push(1) man page states:\n\n> Usually, \"git push\" refuses to update a remote ref that is not an\n> ancestor of the local ref used to overwrite it.\n>\n> This option overrides this restriction if the current value of the\n> remote ref is the expected value. \"git push\" fails otherwise.\n>\n> --force-with-lease alone, without specifying the details, will protect\n> all remote refs that are going to be updated by requiring their\n> current value to be the same as the remote-tracking branch we have for\n> them.","distinct":false,"url":"https://api.github.com/repos/thoughtbot/guides/commits/150d2d67ca743cd8f99db7f994d79fd2c5683673"}]}