[Bug] Stacked PR squash merges can combine the PR author's name with the merger's email
- 主要語言
- Go
- 星號
- 1.5k
- 分支
- 70
- 平均合併
- 1 天 8 小時
- 30 天內合併 PR
- 7
描述
## Description
When a native GitHub Stacked PR is squash-merged by someone other than the PR author, the generated commit can contain a mixed author identity:
- The Git author name belongs to the PR author.
- The Git author email belongs to the user who merged the stack.
The original commits are correctly associated with the PR author. The incorrect email is introduced when GitHub creates the squashed commit.
As a result, the repository page may display the PR author's name while the API, contribution graph, contributor statistics, and other author-based tooling attribute the commit to the merger.
## Public examples
- [web-infra-dev/rslint PR #1461](https://github.com/web-infra-dev/rslint/pull/1461) → [generated squash commit](https://github.com/web-infra-dev/rslint/commit/848cda7e34a69462bfe311cbd21885fe3b02c66e)
- [vercel/next.js PR #96274](https://github.com/vercel/next.js/pull/96274) → [generated squash commit](https://github.com/vercel/next.js/commit/a619237b1c1356618f287289213031e0a95dd2a1)
貢獻指南
研究方向
No source file, test, or entry point is identified. Start by comparing the linked pull requests with their generated squash commits and determine whether gh-stack has a relevant merge path; done should mean the mixed author identity is reproducibly explained and a concrete project-scoped change is defined.
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- git, github
- 領域
- cli
- Issue 類型
- 缺陷
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 活躍
- 描述清晰度
- 需要釐清
- 新手友好度
- 30/100