You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+22-33Lines changed: 22 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Contributing to codecompanion.nvim
1
+
# Contributing to CodeCompanion.nvim
2
2
3
3
Thank you for considering contributing to CodeCompanion.nvim! This document provides guidelines and information to help you get started with contributing to the project.
4
4
@@ -38,44 +38,34 @@ CodeCompanion.nvim is organized into several key directories:
38
38
### Prerequisites
39
39
40
40
- Neovim 0.10.0+
41
-
-[lua-language-server](https://github.com/LuaLS/lua-language-server) for LSP support
41
+
-[lua-language-server](https://github.com/LuaLS/lua-language-server) for LSP support and type annotations
42
42
-[stylua](https://github.com/JohnnyMorganz/StyLua) for Lua formatting
43
43
44
44
### Setting Up for Development
45
45
46
-
1. Clone your fork of the repository
47
-
2. Create a minimal configuration for testing:
46
+
> This section explain how to setup the environment for development using lazy.nvim package manager. However you can use the package manager of your choice.
47
+
48
+
1. Clone your fork of the repository.
49
+
2. Define codecompanion configuration pointing to your local repository:
-- Include any optional dependencies needed for your development
71
59
},
60
+
opts= {
61
+
opts= {
62
+
log_level="DEBUG", -- For development
63
+
},
64
+
-- The rest of your configuration
65
+
}
72
66
}
73
-
74
-
require("lazy.minit").repro({ spec=plugins })
75
67
```
76
68
77
-
3. Launch Neovim with your minimal config: `nvim --clean -u minimal.lua`
78
-
79
69
## Debugging and Logging
80
70
81
71
### Logging
@@ -115,8 +105,7 @@ When adding new features, please include tests in the appropriate test file unde
115
105
- Use [stylua](https://github.com/JohnnyMorganz/StyLua) for formatting Lua code
116
106
- Configuration is in `stylua.toml`
117
107
- Run `make format` to format the code before submitting a PR
118
-
- Type annotations are encouraged (see `lua/codecompanion/types.lua`)
119
-
- Use meaningful docstrings for functions with the standard LuaDoc format
108
+
- Type annotations are encouraged (see `lua/codecompanion/types.lua`) and [LuaCATS site](https://luals.github.io/wiki/annotations/)
120
109
121
110
## Building Documentation
122
111
@@ -130,7 +119,7 @@ make docs # Generate plugin documentation
130
119
131
120
-**Feature Requests**: Please suggest new features, but note that only features that align with the maintainer's workflow may be accepted.
132
121
-**Bug Fixes**: When submitting a PR for a bug, ensure you've first raised an issue that can be recreated.
133
-
-**Responsibility**: If you add a feature, you are responsible for maintaining and bug fixing that feature going forward.
122
+
-**Responsibility**: If you add a feature, you are responsible for maintaining and bug fixing that feature going forward. The maintainers may provide guidance and support, but ultimate responsibility lies with the contributor.
134
123
-**Code Quality**: Strive to maintain high code quality with proper tests.
135
124
-**Communication**: If you have questions, open an issue or reach out to the maintainers.
136
125
@@ -151,4 +140,4 @@ When facing issues during development, try these steps:
151
140
4. Reference any related issues in your PR description
152
141
5. The PR should be based on a prior discussion unless it's a straightforward bug fix
0 commit comments