From b9f393f6b76b68d8a55ed3a8d57419437f84e060 Mon Sep 17 00:00:00 2001 From: Mika Vilpas Date: Mon, 8 Jul 2024 11:52:30 +0300 Subject: [PATCH] docs: add section on providing feedback on upcoming features (#160) --- COMMUNITY.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/COMMUNITY.md b/COMMUNITY.md index 5f4bd506..189f41e7 100644 --- a/COMMUNITY.md +++ b/COMMUNITY.md @@ -8,6 +8,8 @@ I started this project because I think it's fun to build cool things, and also to learn how to build a neovim plugin. I have been very happy to see that many people have found this useful. +This document lists some ways you can contribute to this project. + ## Please share your ideas and feedback There are many different kinds of people using this. I have been programming @@ -28,3 +30,16 @@ I want to encourage you to share your ideas and feedback: - give feedback on upcoming features and development ideas - tip: you can use the GitHub `watch` feature to get notified about new discussions and comments. + +## Provide feedback on upcoming features + +Generally, all new features will be opened as pull requests on GitHub. If you +want to provide feedback on upcoming features, you can + +- follow new pull requests on GitHub (e.g. set + `watch -> custom -> pull requests`) +- similarly, follow issues + +To test pull requests locally, you can use `branch = "feature-branch-name"` in +your lazy.nvim plugin spec. See the lazy.nvim documentation for more +information: .