Skip to content

Blame width not adjustable. #599

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
Closed
BanksySan opened this issue Nov 6, 2021 · 1 comment
Closed

Blame width not adjustable. #599

BanksySan opened this issue Nov 6, 2021 · 1 comment
Assignees
@per1234
Labels
conclusion: resolved Issue was resolved topic: code Related to content of the project itself type: imperfection Perceived defect in any part of project

Comments

@BanksySan
Copy link

Describe the bug
When I view the blame annotations the width of the blame window is about 50% of the code window which makes it very difficult to work with.

To Reproduce
Steps to reproduce the behavior:

  1. Create a Git repo and some commits.
  2. Open file with a history.
  3. Right-click and show blame annotations
  4. Try to change size of window.

Expected behavior
Reduce size of window so that I can clearly see the code.

Screenshots
Blame annotations window

Desktop (please complete the following information):
Processor Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz 2.30 GHz
Installed RAM 32.0 GB (31.9 GB usable)
System type 64-bit operating system, x64-based processor
Pen and touch Pen and touch support with 10 touch points

Edition Windows 11 Home
Version 21H2
OS build 22000.282
Experience Windows Feature Experience Pack 1000.22000.282.0
@BanksySan BanksySan added the type: imperfection Perceived defect in any part of project label Nov 6, 2021
@per1234 per1234 added the topic: code Related to content of the project itself label Nov 8, 2021
@per1234 per1234 assigned per1234 and unassigned fstasi May 26, 2024
@per1234
Copy link
Contributor

per1234 commented May 26, 2024

Obsoleted by the removal of the Git extension in #1018

@per1234 per1234 closed this as completed May 26, 2024
@per1234 per1234 added the conclusion: resolved Issue was resolved label May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@per1234 per1234

Labels
conclusion: resolved Issue was resolved topic: code Related to content of the project itself type: imperfection Perceived defect in any part of project
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@BanksySan @fstasi @per1234