It's good but on production branch rebasing will change the commit history with it.
Git-blame-someone-else
61–70 of 100 posts
Re: Git-blame-someone-else
#62If you sign your commits, you can't claim that somebody else rewrote the Git history with you as the author. Plausible deniability...
Conversely, if you do sign your commits but are careless if your keys (e.g. storing your private-key directly in your repo...) then you've got even more work for yourself.
Re: Git-blame-someone-else
#63This has saved me so many times. I’m sure I would have lost my job a while ago had I not been able to use this, it’s one of my most actively use tools. I’m sure eventually I’ll be losing my job, but at least this repo has enabled me to keep it a little bit longer.
Curious how do you get away with it without anyone noticing. Doesn’t this imply rewriting the master branch? Wouldn’t that cause noticeable issues for everyone else? Or maybe you’re the only active contributor on that codebase (but then who else can you blame?)
Clearly a satirical joke.
Re: Git-blame-someone-else
#64Others were to blame for past threads: Git Blame-Someone-Else - https://news.ycombinator.com/item?id=21004193 - Sept 2019 (66 comments) Git-blame-someone-else – Blame someone else for your bad code - https://news.ycombinator.com/item?id=11049993 - Feb 2016 (65 comments)
[deleted]
Re: Git-blame-someone-else
#65This is a great example of why you should enable vigilant mode [1] on your GitHub account and set your machine up to GPG sign your commits. [1] https://docs.github.com/en/github/authenticating-to-github/m...
But if you gpg sign your commit Now all your contributors will have to sign their next commits too. My workmates would hate me if i introduced this to production.
Why do they have to sign their commits? Their contributions are unverified, as are any commits made in your name without your signature, but they don't have to do anything.
You gain the ability to prove that a certain commit came from your machine or someone with full access to it, they don't.
To be honest, everyone should be signing their commits in a professional environment. It takes minutes of work to set up and greatly increases the trust you can have in the code base.
If you're scared of affecting your workflow, just don't protect the GPG keys with a password (dangerous) or use your operating system's trust store to unlock them at login (less dangerous, but still suboptimal).
I sign my work commits without ever entering a password in a prompt. Some of my coworkers also sign their commits, most of them don't.
Re: Git-blame-someone-else
#66Earlier quoted context omitted.
Curious how do you get away with it without anyone noticing. Doesn’t this imply rewriting the master branch? Wouldn’t that cause noticeable issues for everyone else? Or maybe you’re the only active contributor on that codebase (but then who else can you blame?)
As someone else is saying, its obviously a joke. Even a halfway intelligent person would be able to create an alibi that they didnt do it.
Of course they didn’t do it. It was somebody else.
Re: Git-blame-someone-else
#67This is hilarious! Got a good laugh from this. It also illustrates how easy it is to impersonate other people in Git. I’m surprised this isn’t discussed more. To be honest, when you really think about it, any commit that is not GPG signed is unverifiable. It could be anybody. I wish signing commits was more widespread.
yeah, we recently started switching from mercurial to bitbucket (not our choice) and we took the time to make commit signing mandatory, piggybacking on the infrastructure that was already in place to sign the mercurial commit, but with new gpg keys as the mercurial commits were signed with p12 keys, which are not supported by git/bitbucket (can't remember which).
Re: Git-blame-someone-else
#68Anyone else pick up on the Fred Randall reference?
Re: Git-blame-someone-else
#69Earlier quoted context omitted.
Does it feel like gardening? Moderating HN that is. It'd have to be one of those "wild gardens" that's mostly the plants doing what they want with a bit of nudging. Pull out a weed here, tie up some branches there, clear the path, give a little extra water to something that didn't get a good chance yet, etc. Sorry for the OT, I was just curious if that analogy resonated.
Probably more like a farm, full of pests and dog poop
I think you mean bullshit and pig swill.
Re: Git-blame-someone-else
#70In a similar vein, I’m the author of git-self-blame: https://github.com/JacobEvelyn/git-self-blame
(Still among the best-commented code I’ve ever written.)