Midwest Dev Chat


  • The newest 15 messages in the super-cool #git channel.

  • 05/18 13:26:52 Majorie: I think I’ve run into that issue where I “fix” a commit in a previous version by changing something I know I need to be deleted, and then there is a commit later in the rebase I have a commit that does the identical change that I already duplicated, so the commit is left with nothing to do at that point
  • 05/18 13:27:31 Majorie: I probably didn’t describe that well slightly_smiling_face
  • 05/18 13:28:58 Marylouise: you're perfect
  • 05/18 13:30:18 Melida: have done that to myself twice in the last week
  • 05/18 13:30:37 Melida: `--skip` always feels dirty
  • 05/18 13:31:07 Majorie: Image File [click to view]
  • 05/18 16:41:31 Alexandria: there's not much point in keeping a no-op commit in your repo history
  • 05/18 16:54:29 Majorie: I have only ever found one reason
  • 05/18 16:54:43 Majorie: actually, I probably could’ve deleted it, so nevermind
  • 05/19 09:46:43 Marylouise: @Alexandria indeed. In the process of squashing lots of commits I had to multi-step the squashes cause it went sideways anytime any pair was a no-op ----- on my road to non-empty commits
  • 05/22 11:18:23 Georgetta: How do I get git to show me refs for a folder which doesn’t exist in my current branch. I know it exists in some branch, but not sure which (and there are several). Feel like this is `git reflog` but not sure.
  • 05/22 11:23:06 Sofia: So when you already `flogged` the repo and it didn't tell you where the treasure was hidden so you have to `reflog` troll
  • 05/22 11:47:00 Lois: you can try something like `git log -g --stat -- <path to folder>`
  • 05/22 11:47:17 Lois: which is the reflog, but that only works if you've had that branch checked out semi-recently
  • *Usernames have been changed to protect the innocent.
We're currently 1059 members strong. Join us!
Request Invite

Check out all the cool channels!

Join the conversation!