Skip to content
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.

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

fix(blame-nvim): Align the git blame window properly when using heirline #864

Merged
merged 1 commit into from
Apr 10, 2024

Conversation

rameshsanth
Copy link
Contributor

📑 Description

Before fix

Screenshot 2024-04-10 at 10 34 17 AM

After fix
Screenshot 2024-04-10 at 10 35 21 AM

ℹ Additional Information

Copy link

github-actions bot commented Apr 10, 2024

Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

  • If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

  • If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

  • Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

  • README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

  • Proper usage of opts table rather than setting things up with the config function.

Copy link
Member

@mehalter mehalter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@mehalter mehalter changed the title fix: Align the git blame window properly when using heirline fix(blame-nvim): Align the git blame window properly when using heirline Apr 10, 2024
@mehalter mehalter merged commit eee1a14 into AstroNvim:main Apr 10, 2024
15 of 16 checks passed
This was referenced Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants