Programming

17424 readers

45 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Unsigned Commits (blog.glyph.im)

submitted 9 months ago by AnActOfCreation@programming.dev to c/programming@programming.dev

25 comments fedilink hide all child comments

I'm curious to hear what the Lemmy programming community thinks of this!

The author argues against signing Git commits, stating that it adds unnecessary complexity to systems.
The author believes that signing commits perpetuates an engineering culture of blindly adopting complex tools.
The consequences of signing Git commits are likely to be subtle and not as dramatic as some may believe.

Archive link: https://archive.ph/vjDeK

you are viewing a single comment's thread
view the rest of the comments

[–] eager_eagle@lemmy.world 2 points 9 months ago

I just like seeing the green badge.

I wouldn't expect or ask others to do it in normal circumstances. FWIW, there might be a (marginal) advantage of using it though:

Here’s the only one that might convince me to start signing commits someday. The high level issue is that the author of a commit is whoever shows up in the Author: field, which can be any random string. GItHub manages permissions on a repo using a GitHub account, which may or may not use the same email addresses in a commit. Anyone can push commits to their own repositories with anyone else’s email address.

src