git commit -m "message" --author=
You can even pass a different commit date with --date=.It's actually a really useful feature when you're migrating a project from a different SCM system to git.
81–90 of 198 posts
git commit -m "message" --author=
You can even pass a different commit date with --date=.It's actually a really useful feature when you're migrating a project from a different SCM system to git.
I don't get it, I never really looked at github comments before. Why are these comments so low-quality? Aren't developers who commit to github the only readership?
Oddly enough my comment itself was altered to be a mindless obnoxious comment! (does github use git commits to track the comments themselves?)
One workaround would be to remove any public email address you commit under from your Github profile. Github uses these email addresses to tie back to your user profile so if you don't want commits pointing at your profile, don't tie email addresses to your profile. Perhaps some mechanism is called for here for approving tying back to your user on new repositories or making any repository not owned by you or your org…
My github profile email is different from my git author email. The latter is even more accessible. Just run git-log on any repository an author has committed to.
git should really make it possible to use openssh/openssl keys for signing - so that I have one key both to push to github and sign my commits. I know that they can be converted from one form to another ... but its really inconvenient, especially on Windows, etc. The GPG key is designed for a email based collaboration flow - that Linus uses. But most of us use Github or Bitbucket's UI to collaborate. Github/Bitbucket…
I have since switched to using my YubiKey and GPG for SSH authentication on pretty much everything, as well as using it to sign my tags in my public git repositories. I don't think I would want to go back to moving keys between devices or setting up unique keys on each device now that I've got my YubiKey set up. Worth the investment, in my opinion.
I can imagine a scenario where a malicious employee is intentionally injecting malicious code (backdoor, whatever) and wants that commit tied back to someone else (their enemy, boss).
If they have push access, would github log who actually pushed it (i.e. ssh key)?
(Or at least they won't provide those push logs to the Apache Software Foundation, which is how I know this.)
Earlier quoted context omitted.
I 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.
Should professors really be spending their time locking down all the ways students may try to cheat? At Caltech, proctoring exams (for example) is not allowed by institute policy. A student's honor that he didn't cheat is considered good enough.
Earlier quoted context omitted.
I 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.
Your comment basically reads, "I cheated and got away with it, and I'm proud of it too. I'm so awesome! Take that, stupid professor!"