| Name | What it does | Why helpful for checking commits / trees |
|---|---|---|
| GitLens | Enhances built‑in Git support: inline blame, commit graph, file history, authorship, etc. GitKraken+2gitlens.amod.io+2 | You can see a visual graph of commit history, check who made what changes, when. Very handy to determine “best commits” or compare contributions. |
| Git Graph | Shows a graphical history of your repository — commits, branches, merges, etc. gdevops.frama.io | Useful for seeing branching and merging structure, visually seeing where work diverged and what commits are where. |
| Git Tree Compare | Allows you to diff your working tree against a branch, tag, or commit in a tree‑view form. VsixHub.com+1 | Helps you see all file‑level changes at once in a tree view when comparing versions. Good for pull requests / merge previews. |
| RepoTree | Generates a visual tree representation of directories/files in your repo. GitHub | If you want to see structure of the project (which files/folders exist) easily, helps with navigation and code review. |
| Project Tree | Lets you maintain a tree layout of the project in explorer pane; remembers open files/tabs etc. GitHub | Useful for getting consistency in how different team members see structure, also helps navigate large projects. |
🔧 If you meant full Visual Studio (Windows, .NET)
If you meant Visual Studio (not VS Code), there are things like:
-
Git Tools / Git Extensions for Visual Studio — built‑in or plugin‑add ons that show history, diffs, authorship.
-
SourceTree or TortoiseGit — external GUIs that can show visual trees of commits, branches; you can use them alongside Visual Studio.
-
CodeLens (in Visual Studio) — shows in the code editor who changed lines, when, etc.
No comments:
Post a Comment