#gerrit — Public Fediverse posts

Yankees Social Media Spotlight: Remembering John Sterling https://www.rawchili.com/mlb/695601/ #AaronJudge #BaltimoreOrioles #Baseball #Brewers #CCSabathia #gerrit #GleyberTorres #JalenBrunson #JohnSterling #Knicks #Milwaukee #MLB #NewYork #NewYorkYankees #NewYork #NewYorkYankees #YankeeStadium #Yankees

Yankees Social Media Spotlight: Remembering John Sterling https://www.rawchili.com/mlb/695601/ #AaronJudge #BaltimoreOrioles #Baseball #Brewers #CCSabathia #gerrit #GleyberTorres #JalenBrunson #JohnSterling #Knicks #Milwaukee #MLB #NewYork #NewYorkYankees #NewYork #NewYorkYankees #YankeeStadium #Yankees

#EUGEN #HADAMOVSKY www.perplexity.ai/search/new?q... #GERRIT #PAAPE advanced-search.allgraph.ro/advanced-sea... #JOANNE #CICONTE search.brave.com/ask?q=Analyz... www.paypal.com/donate?busin... aePiot: Semantic nodes: The new SEO currency. Build yours now.

Perplexity

#EUGEN #HADAMOVSKY www.perplexity.ai/search/new?q... #GERRIT #PAAPE advanced-search.allgraph.ro/advanced-sea... #JOANNE #CICONTE search.brave.com/ask?q=Analyz... www.paypal.com/donate?busin... aePiot: Semantic nodes: The new SEO currency. Build yours now.

Perplexity

𝗜𝘀𝗮𝗯𝗲𝗹𝗹𝗮 𝗲𝗻 𝗚𝗲𝗿𝗿𝗶𝘁 𝘃𝗲𝗿𝗿𝗮𝘀𝘁 𝗱𝗼𝗼𝗿 𝘇𝘄𝗮𝗻𝗴𝗲𝗿𝘀𝗰𝗵𝗮𝗽 𝗶𝗻 𝗜𝗸 𝗩𝗲𝗿𝘁𝗿𝗲𝗸 𝗫𝗟: '𝗛𝗼𝗲 𝗸𝗮𝗻 𝗱𝗶𝘁 𝗻𝗼𝘂?'

Kort nadat Isabella en Gerrit, te zien in 'Ik Vertrek XL', zich hebben gevestigd in Oostenrijk, krijgt het gezin onverwacht nieuws te verwerken. Isabella is zwanger.

https://www.rtl.nl/boulevard/entertainment/artikel/5552429/isabella-gerrit-ik-vertrek-xl-zwangerschap-ongepland

#Isabella #Gerrit #zwangerschap

Looks like all the bugs I reported against #Gerrit back in 2014 have finally been closed as Won't Fix (Obsolete). Classic.

I had forgotten, but back then I was quite upset by the "new change screen" in version 2.8. (#Wikimedia is now running on 3.10.6.)

https://issues.gerritcodereview.com/issues/40002576
https://issues.gerritcodereview.com/issues/40002579
https://issues.gerritcodereview.com/issues/40002302
https://issues.gerritcodereview.com/issues/40002527

Is it possible to do any diff between a PR's force-pushes on GitHub? I know there is a Compare next to each force-push, but it completely fails if there was rebase (compares all the rebased code), and you cannot aggregate compares for multiple force-pushes without doing that manually.
At least with emails, one sends a changelog between series; Gerrit and GitLab do have a serious per-version review of changes. Forgejo's review UI seems as broken as GitHub.
How does anyone do any serious iterative reviewing on GitHub or Codeberg?

#GitHub #Gerrit #GitLab #Codeberg

Gerrit Misconfiguration Exposed Google Projects to Malicious Code Injection https://www.securityweek.com/gerrit-misconfiguration-exposed-google-projects-to-code-injection/ #Vulnerabilities #vulnerability #SupplyChain #GerriScary #Gerrit #google

Gerrit Misconfiguration Exposed Google Projects to Malicious Code Injection https://www.securityweek.com/gerrit-misconfiguration-exposed-google-projects-to-code-injection/ #Vulnerabilities #vulnerability #SupplyChain #GerriScary #Gerrit #google

@douginamug and I are trying to debug a #Gerrit login issue in the #wmhack lobby. Looks like creating a new Wikitech account and rigourously following the tutorial doesn't let us SSH to Gerrit. Could it be related to the recent downtime? Join us on the couch in front of the registration desk! :-) https://www.mediawiki.org/wiki/Gerrit/Tutorial

#wikitech #ssh #git

GitHub's Legacy Of Terrible Code Review,
by @thcipriani

https://tylercipriani.com/blog/2024/08/31/the-pull-request/

#GitHub #GitLab #codereview #GerritCodeReview #Gerrit

Effective code review through natural stacking and meaningful comment messages, by @gerritreview

https://gitenterprise.me/2025/03/10/gerrit-code-review-a-how-to-guide-for-new-users/

#GerritCodeReview #Gerrit #Rietveld

@leitmedium letztlich bietet ein Repository selbst alles was man dazu braucht.

Es ist nur ein, durch die von GitHub etablierte "Unart" immer einen User-spezifischen Fork anzulegen, entstandenes Problem, welches Oberhaupt erst zu diesem Overhead im Workflow führt.

#Gerrit, auch wenn ich dessen UX stark verbesserungswürdig finde, verfolgt hier einen nativeren Ansatz, bei welchem alle im gleichen Repository arbeiten und jeweils innerhalb eines refs ihre Arbeit vornehmen können.

Has someone attempted to build a #CodeReview tool that relies more on #git itself like using git notes and git trailers and such?

#VersionControl #VCS #PullRequest #MergeRequest #GitHub #BitBucket #GitLab #Gerrit #Gitea #forgejo #Codeberg #amCoding #amProgramming #softwareDevelopment #softwareEngineering #webDevelopment

Стилистический-Анализатор: Проверка Наличия Комментария в Конце Фигурной Скобки

Настал тот первый день, когда в программировании микроконтроллеров наконец пригодилась такая абстрактная структура данных как стек LIFO . У нас в организации существует обязательное внутреннее требование к оформлению исходных кодов на языке программирования Си для микроконтроллеров, которое звучит так: В конце каждого блока if(...) {...} ; switch(...) {...} ; for(...) {...} и т.п. необходимо пиcать комментарий // end of if(...). end of switch(...) end of for(...) соответственно. Я написал консольную утилиту, которая автоматически находит аномалии в коде согласно этому правилу.

https://habr.com/ru/articles/865536/

#codestyle #цензура #gerrit #code_review #стилистический_анализ #комментирование_кода #комментирование #С #lifo #стек

Стилистический-Анализатор: Проверка Наличия Комментария в Конце Фигурной Скобки

Настал тот первый день, когда в программировании микроконтроллеров наконец пригодилась такая абстрактная структура данных как стек LIFO . У нас в организации существует обязательное внутреннее требование к оформлению исходных кодов на языке программирования Си для микроконтроллеров, которое звучит так: В конце каждого блока if(...) {...} ; switch(...) {...} ; for(...) {...} и т.п. необходимо пиcать комментарий // end of if(...). end of switch(...) end of for(...) соответственно. Я написал консольную утилиту, которая автоматически находит аномалии в коде согласно этому правилу.

https://habr.com/ru/articles/865536/

#codestyle #цензура #gerrit #code_review #стилистический_анализ #комментирование_кода #комментирование #С #lifo #стек

Стилистический-Анализатор: Проверка Наличия Комментария в Конце Фигурной Скобки

Настал тот первый день, когда в программировании микроконтроллеров наконец пригодилась такая абстрактная структура данных как стек LIFO . У нас в организации существует обязательное внутреннее требование к оформлению исходных кодов на языке программирования Си для микроконтроллеров, которое звучит так: В конце каждого блока if(...) {...} ; switch(...) {...} ; for(...) {...} и т.п. необходимо пиcать комментарий // end of if(...). end of switch(...) end of for(...) соответственно. Я написал консольную утилиту, которая автоматически находит аномалии в коде согласно этому правилу.

https://habr.com/ru/articles/865536/

#codestyle #цензура #gerrit #code_review #стилистический_анализ #комментирование_кода #комментирование #С #lifo #стек

Стилистический-Анализатор: Проверка Наличия Комментария в Конце Фигурной Скобки

Настал тот первый день, когда в программировании микроконтроллеров наконец пригодилась такая абстрактная структура данных как стек LIFO . У нас в организации существует обязательное внутреннее требование к оформлению исходных кодов на языке программирования Си для микроконтроллеров, которое звучит так: В конце каждого блока if(...) {...} ; switch(...) {...} ; for(...) {...} и т.п. необходимо пиcать комментарий // end of if(...). end of switch(...) end of for(...) соответственно. Я написал консольную утилиту, которая автоматически находит аномалии в коде согласно этому правилу.

https://habr.com/ru/articles/865536/

#codestyle #цензура #gerrit #code_review #стилистический_анализ #комментирование_кода #комментирование #С #lifo #стек

@koopa @hikari

https://review.opendev.org/ is #Gerrit for #OpenStack, but my personal experience is that Gerrit is better in theory than in practice. I had to use it for some internal tools in #RedHat for some time (a long time ago) and the experience was absolutely horrible (see https://youtu.be/L8OOzaqS37s?t=485 … @gregkh is much smarter than me). I agree with you on the rest, GH-style PRs are actually quite unpleasant when once gets used to alternatives, I really like #SourceHut and yes #Email is awesome.

i think that GitHub has firmly established some unnecessary preconceptions about how code review should work

if you look at the code forges that came after (GitLab, Gitea), most of them copy the Pull Request interface because it's familiar and easy to use

even though PRs as a concept exist with email-based workflows, [0] these modern code forges assume that PRs are the finest granularity you are working at. there are no accommodations for atomic commits, despite some of Git's tools being designed for this. [1]

having used it over the summer, i do think that #gerrit gets it right. but nobody wants to copy Gerrit when making a comprehensive forge. the closest thing we have is #sourcehut (uses email for submitting patches), which is not really what i want.

as it stands, Gerrit appears to be super underutilized in open-source spaces. the only project i'm aware of (that isn't being operated by a company) that uses it is #TouchHLE by @hikari. [2] aside from the friction of setting Gerrit up to work with a more featureful forge, i think the reason for this may be a resistance to more bureaucracy when working on fun stuff.

but like. reviewing GitHub PRs with more than one commit kinda sucks. yet you don't want to go full Gerrit (+cgit) either, because Gerrit's pipeline integration appears to be pretty primitive. also, it's nice to have a repo browser other than cgit

i think that my ideal setup would be a federated (!) code forge with gerrit-style code review of individual commits and modern CI integration

[0] https://git-scm.com/docs/git-request-pull
[1] https://gerrit-review.googlesource.com/Documentation/intro-rockstar.html
[2] https://github.com/touchHLE/touchHLE

What has been unspoken for a while, is now official. Wikimedia and Mediawiki have essentially halted their transition to Gitlab, because Gitlab Community edition has not been able to provide and be adaptable enough to deliver on the needs of Wikimedia’s complex ecosystem.

Gitlab will remain as the git-light contribution flow for tools and 3rd party developers, while Gerrit will keep serving the most critical flows.

https://www.mediawiki.org/wiki/GitLab/Migration_status

#gitlab #gerrit #git

#Gerrit ma tak koszmary interfejs, że właśnie otwarłem przegląd w odrębnym, prywatnym oknie, żeby sprawdzić, czy moja odpowiedź faktycznie się pokazała, a nie pozostała w stanie "szkicu".

I find #gerrit UI so horrible that I literally open the review in a private window to check whether my reply was actually posted rather than left in some magical "draft" state.

What I absolutely hate, HATE, is when I type "somescript.py" in any app and it automatically converts it to a hyperlink to some random domain in the .py TLD.

Because that's what everybody expects to happen. Because it's most important to the world that everybody links to Paraguay.

I'm looking at you, #confluence #jira #webex #gerrit #atlassian . Stop it.

#python

New contribution experience report: JGit. A somewhat kafkaesque experience, unfortunately.
https://antonin.delpeuch.eu/posts/contribution-experience-report-jgit/
#eclipse #gerrit #git #jgit

@xahteiwi Maybe it is time I properly learned "git review" then, since we are using #Gerrit at $DAYJOB. So far, I have only been using "git review -d" to download changes to test them for review, and nothing else...

I sort of like the Gerrit workflow, it has grown on me. I would like a better way to group changes like Critic did, though. Good thing that there are many ways to do things, so that groups can find a workflow that works for them.

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.

Discuss.

#Gerrit #Git #GitLab

[answered!]

Any of y'all know how #Gerrit works? I've *again* forgotten how to set a patch as dependant on another — is it `Depends-On: {changeid}` in the commit message?

#Wikimedia #MediaWiki

OpenDev отключила инструмент Gerrit после известий о его взломе #взлом, #OpenDev, #Gerrit, #OpenStack https://www.securitylab.ru/news/513288.php https://twitter.com/SecurityLabnews/status/1319247139562770434/photo/1