profile
viewpoint
Eric Amodio eamodio @microsoft MA amod.io Father, husband, code monkey, entrepreneur, geek. Creator of GitLens for VS Code. VS Code developer @Microsoft. Previously @TeamCodeStream.❤ open-source

eamodio/SaveAllTheTabs 53

Quickly save and restore sets of document tabs in Visual Studio

eamodio/fitbit-pure 9

A beautifully designed, customizable, clean and simple clock face for Fitbit Sense & Versa devices

eamodio/eamodio.github.io 6

Personal website

eamodio/gitlens.github.io 5

GitLens website

eamodio/posh-git 2

A PowerShell environment for Git

eamodio/Changelog 1

This VSCode extension provides additional package.json changelog hover hint information.

eamodio/eslint-plugin-prettiest 1

ESLint rules to "fix" prettier formatting

eamodio/github-amethyst-theme 1

A dark theme for GitHub

eamodio/SaveAllTheTime 1

SaveAllTheTime makes it so you never commit files to Git without saving ever again

eamodio/atom 0

:atom: The hackable text editor

issue commenteamodio/vscode-gitlens

Option to list commits in topological order

Hi, I was wondering if there was still someone working on this: it doesn't seem too hard to implement. If not, I could work on it, although I'm not the most familiar with open-source and gitlens so I might need some guidance in the right direction. Thanks! ~andy

laanwj

comment created time in 3 hours

delete branch eamodio/fitbit-pure

delete branch : dependabot/npm_and_yarn/ini-1.3.8

delete time in 5 hours

pull request commenteamodio/fitbit-pure

Bump ini from 1.3.5 to 1.3.8

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

dependabot[bot]

comment created time in 5 hours

startedeamodio/vscode-gitlens

started time in 8 hours

PR opened eamodio/vscode-gitlens

Fixes #1328 - Adds support for reading file history for files which o…

Description

Fixes #1328 - Adds support for reading the file history for files which originate from symlinks

Checklist

<!-- Please check off the following -->

  • [x] I have followed the guidelines in the Contributing document
  • [x] My changes follow the coding style of this project
  • [x] My changes build without any errors or warnings
  • [x] My changes have been formatted and linted
  • [x] My changes include any required corresponding changes to the documentation
  • [x] My changes have been rebased and squashed to the minimal number (typically 1) of relevant commits
  • [x] My changes have a descriptive commit message with a short title, including a Fixes $XXX - or Closes #XXX - prefix to auto-close the issue that your PR addresses
+10 -0

0 comment

1 changed file

pr created time in 16 hours

fork sweiss3/vscode-gitlens

Supercharge the Git capabilities built into Visual Studio Code — Visualize code authorship at a glance via Git blame annotations and code lens, seamlessly navigate and explore Git repositories, gain valuable insights via powerful comparison commands, and so much more

http://gitlens.amod.io

fork in 17 hours

create barncheamodio/vscode-gitlens

branch : insiders

created branch time in 18 hours

delete branch eamodio/vscode-gitlens

delete branch : insiders

delete time in 18 hours

issue commenteamodio/vscode-gitlens

Make separate line history view more discoverable

Ok, yes I see that button now. A separate Line history view would be great, thanks.

On Fri, 15 Jan 2021 at 19:18, Eric Amodio notifications@github.com wrote:

What do you mean by this?

I was surprised that it doesn't just exist as a toggleable option by default like File history.

Do you mean this? Clicking that will toggle between File & Line history. [image: image] https://user-images.githubusercontent.com/641685/104688713-3c034b80-56cf-11eb-848d-ccc2e8053e4f.png

Initially the plan was the completely remove the independent Line History view, since I integrated as a toggle on the File History view, but because enough users still want it as an additional view, I am keeping it.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/eamodio/vscode-gitlens/issues/1217#issuecomment-760678565, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADXYQUCN55K3WLUSWC5ZETSZ7MZZANCNFSM4UFUDAMA .

eamodio

comment created time in 19 hours

issue commenteamodio/vscode-gitlens

Line blame popup disapears immediately once scrolling reaches the top or bottom of the popup

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

cateyes99

comment created time in a day

issue commenteamodio/vscode-gitlens

No way to disable "GitLens would like to connect to GitHub"

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

lexicalunit

comment created time in a day

issue commenteamodio/vscode-gitlens

Avatar position in hover could be moved downward

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

mapringg

comment created time in a day

startedeamodio/fitbit-pure

started time in a day

issue commenteamodio/vscode-gitlens

GitLens does not handle Windows junctions

Thank you - I completely forgot all of this is running inside node.js!

fs.realpathSync does the trick nicely - and so it doesn't look like I'll be needing any extra settings indeed.

Now that I have everything I need, I'll try implementing it tomorrow. If you could perhaps point me to the area in which "git blame" logic resides, that would be awesome.

sweiss3

comment created time in a day

issue commenteamodio/vscode-gitlens

GitLens does not handle Windows junctions

It appears to be true by default. In the case I'm referring to, LinkToRepo2 is not committed in Repo1 - it's actually .gitignore'd (it's a product of a build operation).

So it doesn't really have any effect here.

Regarding junction resolution, I do see that there's a powershell command which can resolve junctions - would that be something I can use?

sweiss3

comment created time in a day

issue commenteamodio/vscode-gitlens

GitLens does not handle Windows junctions

If I go directly to the submodule folder, in that case - I get the complete history as I would expect. I think the issue here stems from using a directory junction, which git does not effectively identify (and it makes sense that it wouldn't).

I agree having an extra setting is less than ideal - searching online I can't say I found a trivial way of resolving a file to its actual location. I will attempt to look further.

sweiss3

comment created time in a day

startedeamodio/vscode-gitlens

started time in a day

issue commenteamodio/vscode-gitlens

GitLens does not handle Windows junctions

Thank you! I think I'm up for the challenge, please note this will be my first venture into the world of VS code plugins :)

Before I start coding, my thought was to enable a new setting, which will allow re-mapping of directories, e.g.:

"gitlens.directoryMappings": {
    "SomeFolder/LinkToRepo2": "R2"
}

Does that make sense?

sweiss3

comment created time in 2 days

issue commenteamodio/vscode-gitlens

Year value shows as 'yyyy' when hovering-over a change

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

jethas-bennettjones

comment created time in 2 days

issue commenteamodio/vscode-gitlens

Add feature to revert series of commits

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Pand9

comment created time in 2 days

issue commenteamodio/vscode-gitlens

Open Changes with Previous broken

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

etiennejcharles

comment created time in 2 days

issue commenteamodio/vscode-gitlens

Search by commit SHA shouldn't require 7 characters

This issue needs more information and has not had recent activity. Please provide the missing information or it will be closed in 7 days. Thanks!

jez9999

comment created time in 2 days

startedeamodio/vscode-gitlens

started time in 2 days

startedeamodio/vscode-gitlens

started time in 2 days

PR opened eamodio/vscode-gitlens

Add on: pull_request trigger to CodeQL workflow

From February 2021, in order to provide feedback on pull requests, Code Scanning workflows must be configured with both push and pull_request triggers. This is because Code Scanning compares the results from a pull request against the results for the base branch to tell you only what has changed between the two.

Early in the beta period we supported displaying results on pull requests for workflows with only push triggers, but have discontinued support as this proved to be less robust.

See https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#scanning-pull-requests for more information on how best to configure your Code Scanning workflows.

+1 -0

0 comment

1 changed file

pr created time in 3 days

fork rneatherway/vscode-gitlens

Supercharge the Git capabilities built into Visual Studio Code — Visualize code authorship at a glance via Git blame annotations and code lens, seamlessly navigate and explore Git repositories, gain valuable insights via powerful comparison commands, and so much more

http://gitlens.amod.io

fork in 3 days

issue openedeamodio/vscode-gitlens

GitLens does not handle Windows junctions

Hi, My setup contains a repo with multiple submodules, with junctions made from submodule A to submodule B.

GitLens is unable to show history of the file when it is accessed through the junction.

Sample directory structure:

Repo1
|- R2 (submodule)
   |- test2.txt
|- SomeFolder
   |- LinkToRepo2 (junction to R2)
       |- test2.txt (from R2)

Navigating to SomeFolder/LinkToRepo2/test2.txt in VSCode results in the following error in GitLens deubg window:

Git Command failed: C:\Program Files\Git\cmd\git.exe -c core.longpaths=true -c core.quotepath=false -c color.ui=false blame --root --incremental -- SomeFolder/LinkToRepo2/test2.txt • no such path 'SomeFolder/LinkToRepo2/test2.txt' in HEAD • 35 ms

I know this is quite a unique case - maybe there's a way I could intercept the command to resolve the correct file and repo on my own?

created time in 3 days

delete branch eamodio/vscode-gitlens

delete branch : insiders

delete time in 3 days

create barncheamodio/vscode-gitlens

branch : insiders

created branch time in 3 days

startedeamodio/vscode-gitlens

started time in 3 days

more