vscode-git-graph icon indicating copy to clipboard operation
vscode-git-graph copied to clipboard

View a Git Graph of your repository in Visual Studio Code, and easily perform Git actions from the graph.

Results 291 vscode-git-graph issues
Sort by recently updated
recently updated
newest added

**Describe the improvement that you'd like** When used on Mac, Ctrl+R open recent folders command in order to easily switch between recent folders. When used while git graph tab is...

improvement

When checking out a commit, Git Graph shows a warning that this results in a detached HEAD stated. If one selects to never display this warning again, this selection is...

improvement

**Describe the feature that you'd like** It would be good if fields like `parent sha`, `author email` and `commiter email` can be hidden, and `date` field format can be customized....

feature request

**Describe the Bug** vscode is stuck after opening the git graph view CPU usage to almost 100% **Steps to Reproduce** Steps to reproduce the behavior: 1. Open git graph view...

bug

- To add the support of viewing commits in reverse order Issue Number / Link: Fixes #645 Summary of the issue: add the optional function: reverse order Description outlining how...

**Describe the Bug** Git Graph fails to open **Steps to Reproduce** Steps to reproduce the behaviour: 1. Cmd-Shift-P "> Git-Graph: View Git Graph (git log)" 2. ``` Error loading webview:...

bug

**Describe the Bug** GitGraph broke on vs code 1.57.0 See https://github.com/microsoft/vscode/issues/125993

vscode-bug
duplicate

**Describe the feature that you'd like** When researching some brilliant projects, it'll be very convenient to follow the author's ideas if we can read the commit history reversely, from the...

feature request

**Describe the Bug** git-graph cannot load all commits. **Steps to Reproduce** Steps to reproduce the behaviour: 1. git clone https://github.com/rusoto/rusoto.git 2. open rusoto project by VSCode 3. open GitGraph view...

bug

**Describe the improvement that you'd like** Currently, comparing any two commits always compares the newer commit (ie. latest in time) versus the older commit, regardless of which commit is clicked...

improvement