GitHub PR Timeline Bug: When 'Master' Isn't the Master Plan for Your Git Development

GitHub PR Timeline Misleads on Merge Destination: A Critical Bug for Development Activities

In the fast-paced world of software engineering, clear and accurate version control feedback is paramount for efficient git development. A recent discussion in the GitHub Community sheds light on a significant bug where the UI timeline for a Pull Request (PR) incorrectly states that code was 'merged into master' when, in reality, it was merged into a feature branch. This discrepancy can lead to confusion, wasted time, and potential missteps in critical development activities.

The Scenario: Dependent PRs and a Misleading Timeline

The reported issue involved a common scenario with dependent pull requests:

• Parent PR: Branch A targeting master
• Child PR: Branch B targeting branch A

The user described a sequence of Git operations performed locally that triggered the bug:

git switch A
git merge B
git merge master
git push origin A

Following these steps, GitHub correctly marked the child PR (B → A) as merged. However, upon inspecting the child PR's timeline, the message displayed was: 'user merged commit sha into master'.

The Discrepancy: UI vs. Reality

This UI message created significant confusion because:

• The parent PR (A → master) was still open.
• The child merge commit was not yet reachable from master.
• The child PR's base branch was still correctly identified as A.

Further verification through the GitHub GraphQL API confirmed the UI's inaccuracy. The API's MergedEvent.mergeRefName and the child PR's baseRefName both correctly reported A as the merge target. Only the UI timeline text was incorrect, naming the default branch (master) instead of the actual feature branch.

Impact on Engineering KPIs and Development Activities

The impact of such a bug on engineering kpis and overall developer productivity is considerable. Misleading information in the PR timeline forces developers to:

• Manually Verify: Teams must spend valuable time inspecting API responses or Git history to confirm the actual merge destination. This adds unnecessary friction to development activities.
• Risk Misunderstandings: Incorrectly assuming code has landed in master can lead to premature deployments, incorrect feature testing, or miscommunications within the team.
• Erode Trust: Inaccurate UI feedback can diminish trust in the platform's reporting, making developers more cautious and less efficient.

This issue highlights the critical need for consistency between the UI and the underlying data, especially in core git development workflows.

What's Next?

While GitHub has acknowledged the feedback, there is currently no official solution or workaround beyond manual verification. This incident, along with a related report concerning other branch name display errors, underscores a potential area for improvement in GitHub's PR timeline accuracy.

For teams engaged in complex development activities with dependent PRs, staying vigilant and cross-referencing information remains key. We encourage the community to engage with the original discussion (Discussion #209384) and share their experiences to help prioritize a fix for this critical git development bug.