TechPrufer
Get started
Microsoft
Microsoft logoMicrosoft · Feature trail

Git Team Activity View

10 posts · Aug 2012 – Jul 2015

What this trail covers

Visual Studio's CodeLens provides in-context information about code changes, authors, associated work items, and incoming changes from other branches. This feature is computed on Team Foundation Server (TFS) and involves a pipeline of jobs: Keepup (processes individual changesets), Aggregator (summarizes and merges data), and Cleanup (removes temporary data). A Catchup job handles historical data processing for existing changesets before TFS 2013. Administration is managed via TFSConfig, and upgrades to Visual Studio 2013 Update 2 CTP2 and Team Foundation Server 2013 Update 2 RC introduce the 'Incoming Changes' indicator, which displays changes occurring in various branches on the code element currently being worked on. This indicator provides visual cues for branch relationships (parent, peer, reverse integration, forward integration, distant, baseless merge) and allows users to compare incoming changes with local versions, view changeset details, track progress in the branch hierarchy, ignore specific branches, hide intermediate branch merges, and connect with the author via IM, Video, Email, Lync Call or Voice Call. Users can also disable the indicator via Tools->Options.

All Microsoft trails
  1. Visual Studio 2015 and CodeLensThis post announces the enhancements to CodeLens in Visual Studio 2015, highlighting feature parity across Git and TFVC version control systems. New features include file-level indicators, a team activity view, and a timeline indicator. It also details the availability and data retention differences between Visual Studio Online and on-premises TFS, and the expansion of CodeLens availability to Visual Studio Professional 2015 and Enterprise 2015. Performance and reliability improvements are also noted.
  2. CodeLens and Team Project RenameThis post explains that CodeLens "just works" after a team project rename, utilizing existing CodeLens files without additional processing. However, it identifies a specific scenario where team project name reuse necessitates re-indexing of CodeLens data. It provides the `TFSConfig CodeIndex /reindexAll` command for TFS and an email request process for Visual Studio Online to re-index data in such cases.
  3. What’s new in CodeLens for Visual Studio 2015 RC?Introduces CodeLens availability in Visual Studio Professional 2015, expanding its reach beyond Enterprise. Enables file-level CodeLens indicators for all file types versioned in Git. Adds combined Authors and When last changed indicators for TFVC, including the time since the last change.
  4. General Availability of CodeLens in Visual Studio OnlineAnnounces the General Availability of CodeLens in Visual Studio Online, a head-up display in the Visual Studio editor that provides in-context information about code. Requires Visual Studio Ultimate 2013 Update 4 or Visual Studio 2015 (Preview or later) and code checked into Team Foundation Version Control in Visual Studio Online. Git repositories in Visual Studio Online already see these indicators with Visual Studio Ultimate 2013 Update 3. Provides a workaround for indicators not appearing by clearing cached data.
  5. CodeLens in Visual Studio Online is now in Public Preview for Europe regionThis post announces the public preview of CodeLens in Visual Studio Online for the West Europe Region. It reiterates the requirements for using CodeLens with Team Foundation Version Control in Visual Studio Online (Visual Studio Ultimate 2013 Update 4 or Visual Studio 2015) and notes that Git repositories already have this functionality with Visual Studio Ultimate 2013 Update 3. It also provides a workaround for a caching issue where CodeLens indicators might not appear.
  7. CodeLens file activity and history now available for C++, JavaScript and SQL files stored in GitThis post introduces the availability of file-level CodeLens team indicators for C++, JavaScript, and SQL files when stored in Git repositories within Visual Studio 2015 CTP6. It details how these indicators appear between the horizontal scrollbar and zoom control, showing when a file was last changed, and enabling a 'Team Activity View' accessible by clicking the author name indicator. This view presents a graphical timeline of commits for the file, color-coded by author, with tooltips for commit details and context-aware actions via right-click. It also covers the 'Changes View' for a list of commits and the 'Work Items' indicator for associated bugs, features, and user stories. The post also mentions collapsing indicators and refresh mechanisms.
  8. CodeLens in Visual Studio Online is now in Public PreviewAnnounces the public preview of CodeLens in Visual Studio Online for customers in North Central & South Central US regions, requiring Visual Studio Ultimate 2013 Update 4 or Visual Studio 2015 Preview and code checked into Team Foundation Version Control. Git repo users already had this functionality since VS Ultimate 2013 Update 3. Provides resources and a troubleshooting workaround for a cache issue.
  9. CodeLens in Visual Studio Online enabled as a Limited CTPThis post announces the limited CTP availability of CodeLens in Visual Studio Online for TFVC repositories, requiring Visual Studio Ultimate 2013 Update 4 or Visual Studio 2015 Preview. It also notes that Git repositories in VSO already have CodeLens indicators enabled with Visual Studio Ultimate 2013 Update 3. A troubleshooting step for cache clearing is provided.
  10. Code Lens for Git "Team Activity View"Introduced the 'Team Activity View' popup for CodeLens in Dev14, replacing the previous popup triggered from the authors indicator. This new view presents commit information graphically, detailing how many changes were done by how many authors over a period of time. Each commit is represented by a shape (dot or triangle) with color mapping to authors, and the horizontal axis shows days since the commit. Hovering reveals commit details, and right-clicking offers contextual actions like viewing commit details or contacting the author. Different shapes denote edits or merges. A legend maps colors to authors, grouping older authors under gray. The view is dockable and adjusts to available horizontal space. This view helps answer questions about code churn and identify knowledgeable individuals for specific code sections.
  11. CodeLens Processing pipeline performance improvementsThis post details performance optimizations for the CodeLens Team Indicators processing pipeline in Team Foundation Server 2013 Update 3. Key improvements include optimized changeset processing for branching and merging operations, reducing time spent on large file changesets. Additionally, temporary CodeLens data is now written in batches, minimizing database and file service operations. These changes result in an average of over 70% improvement in run time for the Keepup and Aggregator jobs.
  12. CodeLens for Git improvements in Visual Studio 2013 Ultimate Update 3 RCThis post details improvements to CodeLens for Git in Visual Studio 2013 Update 3 RC. Key enhancements include automatic refreshing of Git indicators upon source control operations (commit, pull, sync, branch change), improved user experience for large files with many changes by using dimmed placeholders during computation, the addition of "when last changed" information to the author indicator, and the introduction of work item indicators for TfGit when commits are associated with work items. It also explains how commit messages can relate to work items and how the system handles cases where work items are not accessible or associated.
  13. Code Lens for Git in Visual Studio 2013 Ultimate Update 3This post introduces the preview of CodeLens Team indicators for Git in Visual Studio 2013 Update 3 CTP1. Initially, it provides 'Authors' and 'Change' indicators for Git, similar to TfVC but based on Git commits. A key difference is that these indicators are computed client-side, making them available for any Git repository (local, TfGit, GitHub, etc.). The post details the user experience, including commit ID, description, author, and date in the details popup, and contextual actions like viewing commit details and interacting with the author. It also notes that automatic refresh of indicators upon Git operations will be available in a later release, with a manual refresh workaround provided.
  14. CodeLens Team Indicators - Processing PipelineThis post details the processing pipeline for CodeLens Team Indicators on Team Foundation Server. It describes the Keepup, Aggregator, Cleanup, and Catchup jobs, their run frequencies, and characteristics. It also covers administration using TFSConfig, behavior during TFS upgrades, and provides tips for managing large CodeLens files and retention periods.
  15. New CodeLens Indicator–Incoming ChangesIntroduces the 'Incoming Changes' indicator to CodeLens in Visual Studio 2013 Update 2 CTP2 and Team Foundation Server 2013 Update 2 RC. This indicator displays changes occurring in various branches on the code element currently being worked on, providing visual cues for branch relationships and allowing users to compare, view details, track, ignore, or hide intermediate merges. It also offers direct connection to the author.
  16. Showing files with pending changes or files that are open in Visual Studio 2012 Solution ExplorerThis post introduces new filtering capabilities in Visual Studio 2012's Solution Explorer. A new 'Filter' button allows users to display only files that are currently open or only files with pending changes. This addresses the challenge of visual noise in large solutions where glyphs indicating pending changes can be easily missed. The filtering works with TFS and other MSSCCI providers.