News for hackers. Stuff that matters.
Re:Julia Evans: Git rebase, what can go wrong by dkarl on Monday November 06, 2023 @01:36PM (#38166747)
It really pays the effort back, though, when you can figure out why something was done, beyond knowing the feature it was related to, which is all you get with a squash merge.
Re:Julia Evans: Git rebase, what can go wrong by mixmastamyk on Monday November 06, 2023 @05:53PM (#38170317)
Why not document it then? In a place where everyone can read it, instead of only developers.
Re:Julia Evans: Git rebase, what can go wrong by Izkata on Monday November 06, 2023 @07:10PM (#38171202)
...are you suggesting spending hours searching through documentation, hoping to possibly find something relevant, instead of just being able to run "git blame" to see why a specific line was changed?
Re:Julia Evans: Git rebase, what can go wrong by mixmastamyk on Monday November 06, 2023 @09:38PM (#38172504)
I use blame often so sounds like you misunderstood.
Re:Julia Evans: Git rebase, what can go wrong by scme0 on Tuesday November 07, 2023 @05:47AM (#38175362)
But if you're using pull requests, you can just look up the PR to get the reasoning and details of the squash commit. I would argue that if you need it to be separate commits after merging, you should create separate PRs most of the time.