See docs here: https://git-scm.com/docs/gitmailmap
See docs here: https://git-scm.com/docs/gitmailmap
Add .mailmap to repo root #115
Open
eestrada
wants to merge 1 commit from
eestrada/zig.vim:add-mailmap into master
pull from: eestrada/zig.vim:add-mailmap
merge into: ziglang:master
ziglang:master
ziglang:hb/new-keywords
ziglang:mikdusan-zir
eestrada
commented 2025年12月08日 00:44:05 +01:00
eestrada
added 1 commit 2025年12月08日 00:44:06 +01:00
Techatrix
commented 2025年12月19日 19:56:58 +01:00
What is the motivation for adding the mailmap? So that the new email shows up in the git log or similar? Or is there something else I am missing. I had hoped that it would make a difference when looking at commits through the web view but doesn't appear to be the case.
Example on a different repository where master branch has a mailmap: Techatrix/zig.vim@36f9d8257f
What is the motivation for adding the mailmap? So that the new email shows up in the `git log` or similar? Or is there something else I am missing. I had hoped that it would make a difference when looking at commits through the web view but doesn't appear to be the case.
Example on a different repository where master branch has a mailmap: https://codeberg.org/Techatrix/zig.vim/commit/36f9d8257fcc51605639fb8eaf03e73b6acb4057
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.git fetch -u
git switch eestrada-add-mailmap
Sign in to join this conversation.
No reviewers
Labels
Clear labels
https://ziglang.org/news/announcing-donor-bounties
Observed behavior contradicts documented or intended behavior.
This issue is limited in scope and/or knowledge of project internals.
An issue with a third-party project that uses this project.
Solving this issue will likely involve adding new logic or components to the codebase.
An issue related to project infrastructure, e.g. continuous integration.
A task to improve performance and/or resource usage.
No questions on the issue tracker; use a community space instead.
A bug that did not occur in a previous version.
An issue with a third-party project that this project uses.
bounty
https://ziglang.org/news/announcing-donor-bounties
bug
Observed behavior contradicts documented or intended behavior.
contributor-friendly
This issue is limited in scope and/or knowledge of project internals.
downstream
An issue with a third-party project that uses this project.
enhancement
Solving this issue will likely involve adding new logic or components to the codebase.
infra
An issue related to project infrastructure, e.g. continuous integration.
optimization
A task to improve performance and/or resource usage.
question
No questions on the issue tracker; use a community space instead.
regression
A bug that did not occur in a previous version.
upstream
An issue with a third-party project that this project uses.
No labels
bounty
bug
contributor-friendly
downstream
enhancement
infra
optimization
question
regression
upstream
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".
No due date set.
Dependencies
No dependencies set.
Reference
ziglang/zig.vim!115
Loading...
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "eestrada/zig.vim:add-mailmap"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?