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
Add necessary bits to install and enable copilot. #18833
base: main
Are you sure you want to change the base?
Conversation
No need to send users down the rabbit hole of how many legacy ways to install vim plugins... Simply direct them to use the new builtin nvim plugin support.
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
Automatically generated comment
|
Source | Preview | Production | What Changed |
---|---|---|---|
copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md |
fpt ghec |
fpt ghec |
Is the failing test working properly? I forked the docs repo to create a pull request which does not contain any new repo reference and my fork is public https://github.com/georgalis/docs yet,
what |
adjust referenced repo from ``` https://github.com/github/copilot.vim.git ``` to ``` https://github.com/github/copilot.vim ``` I'm not sure this makes a difference with regard to `private repositories` if not, perhaps the test should check PUBLIC_REPOS with .git as valid.
@georgalis Thanks so much for opening a PR! I'll get this triaged for review |
No need to send users down the rabbit hole of how many legacy ways to install vim plugins... Simply direct them to use the new builtin nvim plugin support.
Why:
Closes 19579
What's being changed (if available, include any code snippets, screenshots, or gifs):
add necessary steps to docs
Check off the following:
Writer impact (This section is for GitHub staff members only):