#mergerequest — Public Fediverse posts

idea regarding #code #review:
intentionally adding #bugs into #code to check if the #reviewer discovers them.
if the reviewer does not find them, then their #review is questionable.
of course the added bugs should be removed before merging ;-)

I am wondering if a concept like this already exists ...
#codequality #softwareengineering #quality #software #git #pullrequest #mergerequest

RE: https://social.heise.de/@heiseonlineenglish/116204871378593268

My preferred solution here is CI/CD without code reviews, with 100% code responsibility and AI disclosure per merge request. Anyone using AI must first disclose this and then explain how it has been used. If the code causes a failure, I, and I alone, am liable for it, even at 23:55.

#ai #llm #FckAI #FckLLMs #Amazon #MergeRequest #PullRequest #CICD #SoftwareDevelopment

Everyone who loves GitLab and SVG should vote for: "Render SVG files as images in MR diffs".

https://gitlab.com/gitlab-org/gitlab/-/issues/15284

#GitLab #SVG #MergeRequest #Diff

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