@morenonatural Sorry, the emoji was mainly expressing that we saw the post and are considering the impact on Codeberg / #Forgejo, and how to potentially improve the situation.
Opinion: people who staunchly prefer working with Gerrit, and consider anything else inferior, really love working with git-review. And if git-review were not Gerrit specific they would be just as happy with, say, GitLab.
The process that the git-review/Gerrit combo automates/enforces (one commit per change, automatically generated topic branches, change IDs with cross-project uniqueness) could also work just fine by hooking up git-review with the GitLab API.
@xahteiwi as someone who wants to contribute to OpenStack, the first time I had to work with Gerrit, I instantly hated it because I'm used to Pull Requests / Merge Requests and their workflow. Gerrit feels "wrong" for me.
@piratehonk You're going off topic. This is about people who like Gerrit, not about people who hate it. The latter is a different discussion to be had — in another thread. 🙂
Anybody else using #Gerrit for code reviews?
Most other #Git servers have a repo browser and render markdown. That'd be really helpful for any non-developers, because we try to keep our documentation in Git, but it's a tough ask for any non-developer to learn how to check out a Git repo, just to read the docs.
Is there anything like that out there? I did a quick search for 3rd party tools and plugins, but couldn't find anything. Readonly mirror to e.g. Forgejo would be the last resort.
@mforester gerrithub(.io) exclusively supports GitHub auth, so it's usual for a project to have a browsable remote there.
For self-hosted Gerrit (and Gerrithub, IME) I believe there's a repo browser called "Gitiles" which Gerrit integrates with.
@supergarv
Einer der groessten Vorteile von gerrit: Die commit message ist Teil des Reviews.
Das fuehrt im core zu deutlich ueberdurchschnittlich guten commit messages, und ist ein Riesenvorteil im Vergleich zu vielen anderen Projekten.
Unsere History rockt, ich bin regelmaessig sehr erfolgreich in git Archaeologie unterwegs um herauszufinden warum Dinge so sind wie sie sind.
Over the past ten days or so, #WindEnergy has provided a large fraction of the #UK's #Electricity demand, often above half of it. Even now, it is providing 47% and keeping #Gas down to single figure in percentage terms. There was a lull overnight but the new #storm, #Gerrit is currently the main source.
Over the past ten days or so, #WindEnergy has provided a large fraction of the #UK's #Electricity demand, often above half of it. Even now, it is providing 47% and keeping #Gas down to single figure in percentage terms. There was a lull overnight but the new #storm, #Gerrit is currently the main source.
To think about it, when it comes to #Git, I really hate PR-based workflows provided by #GitHub and #Gitlab. I like squashing my commits and giving them a meaningful message, only to then duplicate that message to PR body, and force-push on amends... All the jumping around PRs is just ugh, not to mention reviewing.
I really want to look into stacked commits workflow, like #Gerrit and stuff, but it's all self-hosted and not widely used...
I wish I could just chain my changes and submit them individually. That's what I kinda do now with branches and gh pr create, but there's still so much involved, it makes me to just say ‘fork all’ and commit to main. I mean, what's the worst that can happen...... yeaaaa.