7 ms·
Kinda hard to not come up with it when setting up your credentials is the first thing git wants you to do before you can commit anything. BTW. You can also over
by seba_dos1 11y ago
Kinda hard to not come up with it when setting up your credentials is the first thing git wants you to do before you can commit anything. BTW. You can also overwrite them by command line switches per commit instead of setting environment variables.
I guess it's worth noting here that you can sign your commits with GPG: https://git-scm.com/book/tr/v2/Git-Tools-Signing-Your-Work https://git-scm.com/book/tr/v2/Git-Tools-Signing-Your-Work
- nailer 11y agoI guess the real uptake is that commits should really be signed by default (eg, by encouraging signing in the tools & ecosystem).
- ultramancool 11y agoReally, this only becomes a problem when services like GitHub link the name up, making it look more legitimate than it is. If they enforced authentication as that user before providing the linking it would be better (perhaps allowing approval of the linking if posted by a different user). Currently it's trivial to make it look like any GitHub user is an actual committer to some sort of egregious or controversial project and users unaware of how GitHub maps this may easily be confused. EDIT: This gets even more disturbing when you realize that GitHub is a site many people list on their resumes and if this association applies from their user page too this could get very bad.
- icebraining 11y agoIt doesn't seem to link in reverse to the user page; at least, I can't find anything on Linus' page related to this repo.
- _delirium 11y agoThere's a Github help page explaining when commits show up in your profile (though worded as an answer for people wondering why one didn't): https://help.github.com/articles/why-are-my-contributions-not-showing-up-on-my-profile/ https://help.github.com/articles/why-are-my-contributions-no... The criteria not fulfilled for this one are that you have to have interacted with the repository on Github in some way. Any one of these criteria would suffice: you're a "collaborator" on the repository, you're a "member" of the organization the owns the repository, you have forked or starred the repository, you have opened a pull request or issue in the repository.
- Maken 11y agoApparently Github doesn't list those faked commits in your profile. Which is anyway a problem because you could be "committing" to who knows what project project without being notified.
- uxcn 11y agoThe simple solution seems to be github just distinguishing between signed and non-signed commits.
- rakoo 11y agoI disagree, the real problem here is people thinking that somehow any github repository can be a trusted source. If you work on Linux, you know that the one and only source of truth is the repo that comes from Linus himself, not anything coming from github.
- icebraining 11y agoLinus doesn't distribute anything himself; you can either have the copy hosted by Github, or the one hosted by a Californian nonprofit called the Linux Kernel Organization, Inc.
- SilasX 11y agoSimilarly, nothing stops you altering the time claimed in the commit. Or -- for that matter -- from taking someone's diff and claiming credit for it. For that reason, I jokingly created `git-upstage`, which streamlines the process of abusing commit edits and plagiarizing code! It squashes a branch, backdates it 5 minutes, and claims you wrote it. https://github.com/SilasX/git-upstage https://github.com/SilasX/git-upstage Edit: Looks like my last commit left the important stuff commented out and can't fix it at the moment. Ah well, you're going to use the tool to rip it off anyway ;-)
- uniformlyrandom 11y agoOh, it appears that git 2.3.2 only allows to go back as far as Dec 2014. That is a pity. I have already prepared a README.md claiming that I have created the internet, but then I failed while trying to backdate it to 1969 (PDT). I was this close to becoming very rich and very evil. Oh well.
- seba_dos1 11y agoDon't give up so easily - you have the source code! ;)
- uniformlyrandom 11y agoI got to my linux workstation, cloned the git repo and dug into the code. Could not figure out how the limitation worked though. Turned out, it did not - the problem was specific to my mac's git. So yes, you can author files from 1970 - it is not a big deal. Thought it was kind of a weird limitation.
- ultramancool 11y agoI love this. Had a project in college that was supposed to be time limited... based on repository times. Oops. Big mistake prof. We rolled back the times on our repo and laughed maniacally about our free 6 hour extension.
- 11y ago
- micampe 11y agoSigning my commits doesn’t prove that I didn’t do an unsigned one.
- sytse 11y agoWe would love support for signed commits in GitLab itself so you can check the signature from the web-interface http://feedback.gitlab.com/forums/176466-general/suggestions/4006354-check-pgp-signed-commits http://feedback.gitlab.com/forums/176466-general/suggestions...