The phrase "... for Neovim" is redundant in a list about Neovim plugins. There's already a line that addresses it as a concept, but this PR adds the phrase explicitly.
I've seen quite a number of recent PRs get delayed waiting for this change, so hopefully it helps
makes the submission process smoother.
Checklist:
The plugin is specifically built for Neovim, or if it's a colorscheme, it supports treesitter syntax.
The lines end with a .. This is to conform to awesome-list linting and requirements.
It's not already on the list.
The title of the pull request is Add/Update/Remove `username/repo` when adding a new plugin.
The description doesn't start with A Neovim plugin for.., or A plugin for...
The description doesn't mention that it's a Neovim plugin, it's obvious from the rest of the document.
Neovim is spelled as Neovim (not nvim, NeoVim or neovim), Vim is spelled as Vim (capitalized), Lua is spelled as Lua (capitalized).
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/rockerBOO/awesome-neovim/pull/637
**Author:** [@assistcontrol](https://github.com/assistcontrol)
**Created:** 12/23/2022
**Status:** ✅ Merged
**Merged:** 12/24/2022
**Merged by:** [@tversteeg](https://github.com/tversteeg)
**Base:** `main` ← **Head:** `main`
---
### 📝 Commits (1)
- [`f251188`](https://github.com/rockerBOO/awesome-neovim/commit/f251188e22c81733e619e19b45d498dad34556dc) PR template: Explicitly forbid "... for Neovim"
### 📊 Changes
**1 file changed** (+1 additions, -1 deletions)
<details>
<summary>View changed files</summary>
📝 `.github/pull_request_template.md` (+1 -1)
</details>
### 📄 Description
See the discussion in #634.
The phrase "... for Neovim" is redundant in a list about Neovim plugins. There's already a line that addresses it as a concept, but this PR adds the phrase explicitly.
I've seen quite a number of recent PRs get delayed waiting for this change, so hopefully it helps
makes the submission process smoother.
Checklist:
- [X] The plugin is specifically built for Neovim, or if it's a colorscheme, it supports treesitter syntax.
- [X] The lines end with a `.`. This is to conform to `awesome-list` linting and requirements.
- [X] It's not already on the list.
- [X] The title of the pull request is ```Add/Update/Remove `username/repo` ``` when adding a new plugin.
- [X] The description doesn't start with `A Neovim plugin for..`, or `A plugin for..`.
- [X] The description doesn't mention that it's a Neovim plugin, it's obvious from the rest of the document.
- [X] Neovim is spelled as `Neovim` (not `nvim`, `NeoVim` or `neovim`), Vim is spelled as `Vim` (capitalized), Lua is spelled as `Lua` (capitalized).
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/rockerBOO/awesome-neovim/pull/637
Author: @assistcontrol
Created: 12/23/2022
Status: ✅ Merged
Merged: 12/24/2022
Merged by: @tversteeg
Base:
main← Head:main📝 Commits (1)
f251188PR template: Explicitly forbid "... for Neovim"📊 Changes
1 file changed (+1 additions, -1 deletions)
View changed files
📝
.github/pull_request_template.md(+1 -1)📄 Description
See the discussion in #634.
The phrase "... for Neovim" is redundant in a list about Neovim plugins. There's already a line that addresses it as a concept, but this PR adds the phrase explicitly.
I've seen quite a number of recent PRs get delayed waiting for this change, so hopefully it helps
makes the submission process smoother.
Checklist:
.. This is to conform toawesome-listlinting and requirements.Add/Update/Remove `username/repo`when adding a new plugin.A Neovim plugin for.., orA plugin for...Neovim(notnvim,NeoVimorneovim), Vim is spelled asVim(capitalized), Lua is spelled asLua(capitalized).🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.