Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • dumb question,why this and even gerrit? github or gitea PR seems much simpler and get the job done well these days
  • Does it use Github's new stacked PR feature?

    Edit: apparently stacked PRs on GH are older than I thought; the readme references a 2024 blog post about it.

  • IME juniors struggle with making single commits in the first place. What I usually see is a scatter brained approach with more "fix" commits than anything else. This doesn't help with that, does it?
  • Sadly doesn't work with git worktrees at all. (As a side note, this is not the first time I observe where go-git and worktrees don't play along nicely).
  • Is it compatible with jujutsu?
  • Who is creating a separate PR for each commit on their feature/fix branch?

    sounds like crazy town.

    I just dont understand why someone would operate like this.

    Lets assume you're squash merging your feature branchs to your local main, then you're raising the them as prs.

    why would you do this?

  • The repo seems to move from "adevinta" (a well known company in the EU tech) to "runetes". Anyone to tell us the story?
  • As someone who much prefers Gerrit's UI/UX over GitHub's UI, I was disappointed that this wasn't replicating the UI for GH reviews.

    Edit: Just to be clear, this is not a blemish on this project. More a lament and a wish someone would create such a thing for those of us forced to leave Gerrit behind for... GitHub. =/

Explore Birbla archives