credit to: Jakub Narębski, Jeff Ferland and Charles Bailey
// this is helpful if you have multiple devs working in a repo and they
// have pulled from dev (or whatever branch) and gotten any of the commits
// you're planning on revertting or you don't/can't know if they have pulled.
// This will set you back to the state of the commit you want without
// overwriting any of the history. This should help prevent conflicts
$ git reset --hard <commit hash you want to revert to>
$ git reset --soft <commit hash of last/latest commit> or @{1}
$ git commit -m "reset: resetting back to # without overwriting history"