Comments by "Gilad Barlev" (@GSBarlev) on "Why Doesn't Curl Merge Pull Requests Properly??" video.

  1. GH "magic words" have been super flaky for me lately. It's probably a tenses issue ("resolve" vs. "resolves") or I need to check the cheatsheet, but honestly my projects are small enough that the extra click is no biggie.
    2
  2. It's a lot of work to fight with the GitHub UI when Git's interactive CLI is honestly 🐐ed for this exact use-case.
    2
  3. If you've never had the chance to do a force-push before... that is exactly what it feels like. Even better when you're bypassing branch protections because you're the repo administrator.
    1
  4. ​ @Kraust It doesn't need to be a force-push, though. It should be an interactive rebase of the PR branch onto the HEAD and a regular push. I didn't quite understand why it's not.
    1
  5. I'm with Daniel (and Linus) on this. GitHub is too aggressive about forcing you to use Git their way. Hell, I remember when "rebase" and "squash" weren't options! For me, the worst part is that release notes are not stored as tag annotations, and the only reason why that I can fathom is really obnoxious vendor lock-in. I still use prefer GitHub over GitLab or bitbucket because the former make my eyes bleed and the latter is owned by the people who develop Jira, but lack of alternatives does not make GitHub good.
    1
  6. Pre-commit is 🐐ed in my experience. The only issue I've had is when I've forgotten to install it 😅, but you can actually enforce it (and even do autofixes) through CI. To ​ @hubertnnn 's point, you do have to properly vet your hooks, but ones I rely on have been rock solid and well-maintained.
    1