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

feat(editing-support): Add cloak.nvim #761

Merged
merged 1 commit into from
Feb 15, 2024
Merged

feat(editing-support): Add cloak.nvim #761

merged 1 commit into from
Feb 15, 2024

Conversation

Uzaaft
Copy link
Member

@Uzaaft Uzaaft commented Feb 14, 2024

Unsure about the folder Ive added it under.

Copy link

github-actions bot commented Feb 14, 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.

@Uzaaft
Copy link
Member Author

Uzaaft commented Feb 15, 2024

R? @AstroNvim/astrocommunity-maintainers

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

@Uzaaft Uzaaft merged commit 47d785d into main Feb 15, 2024
16 checks passed
@Uzaaft Uzaaft deleted the feat/cloak branch February 15, 2024 11:37
mehalter pushed a commit that referenced this pull request Feb 15, 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.

None yet

2 participants