History Mode
GitContext is designed to streamline code reviews, ensuring you never have to review the same code twice if you don't want to. It intelligently tracks your progress, so you only review changes from where you last left off.
Since reviewers are most interested in the evolution of code between reviews rather than individual commits, GitContext snapshots the code each time a review is submitted. These snapshots, called "revisions," form the basis for comparisons in GitContext. You can view the entire timeline of revisions in the history bar, quickly seeing how a pull request has evolved in response to reviews. The history bar also allows you to select any two revisions to see the differences between them, making it easy to track changes from review to review rather than commit to commit. We even visually showcase how far individual participants have reviewed code down to the file level.
History Mode SettingNew
We're excited to introduce more control over how pull request history is tracked. While we believe revisions are the optimal way to review code, we understand that some workflows may require greater control. To accommodate different use cases, we've added a "History Mode" setting for individual pull requests. You can choose between:
- Revisions (default): GitContext will track revisions as reviews are submitted, simplifying your pull request history into intelligent breakpoints for streamlined code reviews.
- Commits: The history bar will show each commit as a potential comparison point, allowing reviewers to examine changes from commit to commit.
Users can switch between these modes at any point during a pull request’s lifecycle according to their needs. We are excited to offer this new level of flexibility in GitContext, helping you tailor the review process to best suit your workflow.