AstroNvim / AstroNvim/astrocommunity
Local leader for git/octo-nvim and ai/opencode-nvim collides
- Dominant language
- Lua
- Stars
- 1.7k
- Forks
- 313
- PR merge metrics
- No merged PRs in 30d
Description
### Checklist
- [x] I have searched through the AstroNvim documentation
- [x] I have searched through the existing issues of this project
- [x] I have searched the existing issues of plugins related to this issue
- [x] I can replicate the bug with the minimal `repro.lua` provided below
### Neovim version (nvim -v)
v0.12.3 release
### Operating system/version
Debian Stable
### Terminal/GUI
kitty
### Describe the bug
"O" is used for both git/octo-nvim and ai/opencode-nvim
https://github.com/AstroNvim/astrocommunity/blob/fe1aabf613f8480bc6414940e018e0215ba93117/lua/astrocommunity/git/octo-nvim/init.lua#L10
https://github.com/AstroNvim/astrocommunity/blob/fe1aabf613f8480bc6414940e018e0215ba93117/lua/astrocommunity/ai/opencode-nvim/init.lua#L15
### Steps to Reproduce
Install both, only opencode-nvim (the last registered) is exposed via "O".
### Expected behavior
Have separate keybiding for each, without collisions. Have a CI job that ensures there's no collisions between plugins.
### Screenshots
_No response_
### Additional Context
_No response_
### Minimal configuration
```Lua
-- AstroCommunity: import any community modules here
-- We import this file in `lazy_setup.lua` before the `plugins/` folder.
-- This guarantees that the specs are processed before any user plugins.
---@type LazySpec
return {
"AstroNvim/astrocommunity",
-- import/override with your plugins folder
{ import = "astrocommunity.git.octo-nvim" },
{ import = "astrocommunity.ai.opencode-nvim" },
}
```
Contributor guide
Research direction
Start with lua/astrocommunity/git/octo-nvim/init.lua and lua/astrocommunity/ai/opencode-nvim/init.lua, then reproduce the collision using the minimal configuration in the issue. Verify that installing both plugins exposes distinct leader bindings, and investigate how the repository could detect collisions in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, lua
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100