home.social

#gitrebase — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #gitrebase, aggregated by home.social.

  1. Nice git experience.

    With A and B being logical streams of development I made a mess:

    main -> A1 -> B1 -> A2 -> B2 -> B3
    \-> A3
    \-> B4 ... B10

    I mixed A, B before noticing the need for 2 branches. I did:

    - Switch to A3, rebase interactively to B1'...B3' A1'...A3'
    - Switch to B3, rebase interactively and delete all the Ai in front
    - Rebase B10 onto B3'.

    I de-mixed two streams of development into their respective branches.😀

    Watch it happen with gitk --reflog.

    #git #GitRebase

  2. 🎉 Behold! A thrilling tale of coders quaking in their boots at the mere mention of "git rebase"😱. Fear not, dear reader, because in this extensive guide, we're assured that the very worst outcome is... wait for it... deleting your work! 🤔💥 Because nothing spells confidence like a digital facepalm.
    brethorsting.com/blog/2026/01/ #gitrebase #codingadventures #digitalfacepalm #programmerhumor #techguides #HackerNews #ngated

  3. 🎉 Behold! A thrilling tale of coders quaking in their boots at the mere mention of "git rebase"😱. Fear not, dear reader, because in this extensive guide, we're assured that the very worst outcome is... wait for it... deleting your work! 🤔💥 Because nothing spells confidence like a digital facepalm.
    brethorsting.com/blog/2026/01/ #gitrebase #codingadventures #digitalfacepalm #programmerhumor #techguides #HackerNews #ngated

  4. 🎉 Behold! A thrilling tale of coders quaking in their boots at the mere mention of "git rebase"😱. Fear not, dear reader, because in this extensive guide, we're assured that the very worst outcome is... wait for it... deleting your work! 🤔💥 Because nothing spells confidence like a digital facepalm.
    brethorsting.com/blog/2026/01/ #gitrebase #codingadventures #digitalfacepalm #programmerhumor #techguides #HackerNews #ngated

  5. 🎉 Behold! A thrilling tale of coders quaking in their boots at the mere mention of "git rebase"😱. Fear not, dear reader, because in this extensive guide, we're assured that the very worst outcome is... wait for it... deleting your work! 🤔💥 Because nothing spells confidence like a digital facepalm.
    brethorsting.com/blog/2026/01/ #gitrebase #codingadventures #digitalfacepalm #programmerhumor #techguides #HackerNews #ngated

  6. Starting Monday off with a nasty Git merge conflict and some rebase loop hell. Because why not.

    #Git #GitRebase

  7. `git rebase -i --rebase-merges`
    allows you to recreate merge commits in the history; absolutely mind blowing

    I hope I'll never use it.

  8. @raboof Oh, nice!

    > the break command (added in Git 2.20)


    Sweet! I've been using the trick originally described, putting a dummy edit after the merge and then resetting back to the merge, for years!

    I absolutely love --rebase-merges and use it many times per day to build and keep track of multiple parallel PRs.

    #git #GitRebase #GitRebaseInteractive

  9. « The command allows you to adjust the history of your repository. It's a useful feature, but of course, mistakes can be made. Use the command to recover. » by Agil Antony on @osdc
    opensource.com/article/23/1/gi

  10. It's still far from finished, but please welcome Bluebird! A Mac app for rewriting git history extremely quickly.

    Reorder commits, amend old ones and fixup any two—with just a drag-and-drop or a couple of keystrokes.
    Never slow down to save workdir changes—they're preserved automatically—and ⌘Z anything, even conflict resolutions.
    It's direct manipulation for git rebase! No special mode needed.

    I still have a lot to do, but boyyy is the app starting to feel useful 😊

    #macos #gitrebase

  11. oh wow this is super useful
    > --fixup=reword:<commit> creates an "amend!" commit which replaces the log message of <commit> with its own log message but makes no changes to the content of <commit>.
    git-scm.com/docs/git-commit#Do…

    #git #gitRebase #gitFixup #gitAutosquash
  12. I just did my first #GitRebase #RebaseMerges and it was awesome.

    So have have these two subfeatures that are independent, and a third subfeature that requires them both, so I make two PRs, feature-1 and feature-2, and one draft. The draft merges the other two and I continue working while people look at the proper PRs.

    I discover something while working on the draft that requires a fix to feature-1. So I just:

    * commit that fix
    * git rebase --rebase-merges $REBASE_BASE --interactive
    * in the rebase-todo, move that fix commit to the section that describes the feature-1 branch
    * [code]git push my_remote $FIX_COMMIT_NEW_ID:feature-1
    * continue working

    awesomesauce