CONTRIBUTING.md (1336B)
1 # Contributing 2 Contributions to nnn are welcome! There's always an open issue with the current ToDo list, which contains the proposed features for the next release you can get your hands on. Any small changes or ideas should go in there, rather than in a separate issue. 3 4 Before suggesting changes, please read a bit about [the design principles nnn follows](https://github.com/jarun/nnn/wiki/concepts#design), and make sure you aren't breaking any of them. 5 6 Feel free to join the [Discussions](https://github.com/jarun/nnn/discussions). We highly recommended a discussion before raising a PR. 7 8 ## Coding standard 9 10 `nnn` follows the Linux kernel coding style closely. The C source code uses TABs and the plugins use 4 spaces for indentation. 11 12 - Code changes should not break the patch framework. Please run `make checkpatches` to ensure. 13 - Run `make shellcheck` if adding/modifying plugins. 14 15 CI runs patch framework sanity test and `shellcheck`. Please watch out for any failures after raising the PR. 16 17 ## Resources 18 The [wiki](https://github.com/jarun/nnn/wiki/Developer-guides) has some resources for developers you might be interested in: building, debugging... 19 20 ## Communication 21 * [Gitter chat](https://gitter.im/jarun/nnn) 22 * [GitHub team](https://github.com/nnn-devs) (if you plan on contributing regularly, ask for an invitation).