-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Commits merged by github have "GitHub <noreply@github.com>" committer #12
Comments
An alternative is to just let the committer field as it, unless it actually is a problem. But at the moment, I don't see what problem it does causes. |
@vogella is looking into a way to disable merge commits |
I don't think it's caused by merge commits, it could be more the "Rebase and Merge" that causes it. |
By the way, merge commits are disabled already. |
AFAIK, this happens if you use "Squash commits..." button in Github, instead of the "Rebase and merge" |
I had created a local branch with first patch. Second patch was merged to the local branch. Later pull request was created with the local branch and merged. And then local branch was deleted. |
Is there anything worth keeping this one open still? |
Looks like there is no one still interested so I guess it's not an issue. |
…tform#12) Add new fragment to platform feature. Signed-off-by: Rolf Theunissen <rolf.theunissen@gmail.com>
I see in Eclipse History that differently to gerrit, where the user that triggered "merge" was recorded as committer, few commits are pushed where the committer is "GitHub noreply@github.com":
Is this something we want / can / should configure globally and document in a policy, or is this responsibility of the individuals to do so, and if yes, hhow it should be done?
See
git log --pretty=fuller
command output:The text was updated successfully, but these errors were encountered: