The lines end with a .. This is to conform to awesome-list linting and requirements.
The title of the pull request is Add/Update/Remove `username/repo` (notice the backticks around `username/repo`) when adding a new plugin.
The description doesn't mention that it's a Neovim plugin, it's obvious from the rest of the document. No mentions of the word plugin unless it's related to something else. No .. for Neovim.
The description doesn't contain emojis.
Neovim is spelled as Neovim (not nvim, NeoVim or neovim), Vim is spelled as Vim (capitalized), Lua is spelled as Lua (capitalized), Tree-sitter is spelled as Tree-sitter.
Acronyms (LSP, TS, YAML, etc.) are fully 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/2047
**Author:** [@DrKJeff16](https://github.com/DrKJeff16)
**Created:** 12/23/2025
**Status:** ✅ Merged
**Merged:** 12/25/2025
**Merged by:** [@DrKJeff16](https://github.com/DrKJeff16)
**Base:** `main` ← **Head:** `feat/jira`
---
### 📝 Commits (1)
- [`3e641ce`](https://github.com/rockerBOO/awesome-neovim/commit/3e641ced7bbae094d4665a655793367c537adc78) Add `letieu/jira.nvim`
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+1 -0)
</details>
### 📄 Description
**NOTE**: I wasn't sure whether put it in the "Note Taking" section or in the current one.
"_Why not the Utility section?_" - Refer to my arguments in #2046.
---
~@letieu Please add a license to your plugin if you intend to have it listed here!
We suggest MIT/Apache-2.0, but it is your choice.~
~Thanks for reading!~
---
### Repo URL:
https://github.com/letieu/jira.nvim
### Checklist:
- [X] The plugin is specifically built for Neovim.
- [x] The plugin is licensed.
- [X] The lines end with a `.`. This is to conform to `awesome-list` linting and requirements.
- [X] The title of the pull request is ```Add/Update/Remove `username/repo` ``` (notice the backticks around ``` `username/repo` ```) when adding a new plugin.
- [X] The description doesn't mention that it's a Neovim plugin, it's obvious from the rest of the document. No mentions of the word `plugin` unless it's related to something else. No `.. for Neovim`.
- [X] The description doesn't contain emojis.
- [X] Neovim is spelled as `Neovim` (not `nvim`, `NeoVim` or `neovim`), Vim is spelled as `Vim` (capitalized), Lua is spelled as `Lua` (capitalized), Tree-sitter is spelled as `Tree-sitter`.
- [X] Acronyms (`LSP`, `TS`, `YAML`, etc.) are fully 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/2047
Author: @DrKJeff16
Created: 12/23/2025
Status: ✅ Merged
Merged: 12/25/2025
Merged by: @DrKJeff16
Base:
main← Head:feat/jira📝 Commits (1)
3e641ceAddletieu/jira.nvim📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
README.md(+1 -0)📄 Description
NOTE: I wasn't sure whether put it in the "Note Taking" section or in the current one.
"Why not the Utility section?" - Refer to my arguments in #2046.
@letieu Please add a license to your plugin if you intend to have it listed here!We suggest MIT/Apache-2.0, but it is your choice.
Thanks for reading!Repo URL:
https://github.com/letieu/jira.nvim
Checklist:
.. This is to conform toawesome-listlinting and requirements.Add/Update/Remove `username/repo`(notice the backticks around`username/repo`) when adding a new plugin.pluginunless it's related to something else. No.. for Neovim.Neovim(notnvim,NeoVimorneovim), Vim is spelled asVim(capitalized), Lua is spelled asLua(capitalized), Tree-sitter is spelled asTree-sitter.LSP,TS,YAML, etc.) are fully capitalized.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.