Combine history views for source code

Problem to solve

As part of Category:Source Code Management we have several different views that provide historical information of how a codebase changes over time:

• Commits - Tracks all changes made for a given repository/branch
• Graph - A visual representation of changes for a given repository/branch
• Blame - Line by line changes of a given file
• Tags - Mark specific points in history as being important

Each has a specific use case, but they share the common goal of tracking history. Our current UI and navigational structure does not provide much connection between them. Some exist as nav menu items, others as a button, and all are displayed on their own separate page/view. The user is forced to understand the existence of each feature, nuances between each, and be able to navigate between them to get a full picture of the history. We are not currently providing much context.

Proposed solution

We should reconsider the information architecture of these features to build better connections between them. We should consider the overall JTBD of understanding how code changes over time to drive possible combinations of views. In addition to navigational improvements, improved connections may give users better insights into how their code is changing over time.