New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Blame still shows N/A after newly created file is committed #123

Closed

zielu opened this issue Jan 29, 2019 · 1 comment

Assignees

Labels

Milestone

Owner

zielu commented Jan 29, 2019 •

edited

Issue exists for new file and also for new segments added to already versioned one

zielu added bug 183 gitlens labels

zielu self-assigned this

zielu added this to the 183.x.y milestone

zielu added the in testing label

zielu added a commit that referenced this issue


          Fixed blame shows N/A for newly committed hunks (#123)

248d62b

zielu added EAP channel labels

Owner Author

zielu commented Feb 11, 2019

Fixed in 183.3.0

zielu closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment