-
-
Notifications
You must be signed in to change notification settings - Fork 856
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FR: mentored projects #1190
Comments
Hi. I would like to start helping with some of this problems, but I'm a CS student and I have barely used github to manage my personal config repo, so I'm very lost about what should I do. I'm not even sure if this is the right place to ask for help about this 😅. I have watched TJ's video about making a PR to Neovim, though. So I think I have to say I want to help on an issue (#1182 for example), clone the Telescope repo and start working on that (?). Sorry for all the questions. |
No need to apologize; everybody was starting out at some point! Here's roughly how you'd start.
Let me know in case you run into any troubles; I think #1182 hopefully already largely lays out how to tackle the issue, if you have more questions don't hesitate to ping me there! |
I'll try working on the bottom_pane preview width @l-kershaw |
Hi all,
since core now engages in mentored projects, I was thinking telescope should maybe follow suit. To that end, here's a list of fixes/features/ideas loosely (and hopefully adequately) sorted from easy to hard the nvim-telescope team is happy to provide guidance on in a PR. Guidance means just open an issue or a first draft PR, lay out how you want to tackle the problem (further) and we'll do our best to help.
_G
analogous tobuiltin.commands
I'll do my best to keep this list up-to-date.
Here's how you'd start
Optionally, you can lay out your solution in the respective issues or a new feature request issue.
The text was updated successfully, but these errors were encountered: