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
Unable to use the GitHub Copilot plugin in Rider #223399
Comments
I worked around this by doing jank stuff. https://gitea.krutonium.ca/Krutonium/NixOS/src/branch/master/user/krutonium-hm-extras/packages.nix#L11-L22 |
Thank you for the suggestion. I gave it a try, but am not familiar with "jank stuff". I did the following, which did not work:
Any suggestions @Krutonium? I should add I also tried without the pkgs. in front of each package as I run home.packages = with pkgs; EDIT: |
You need to add Basically what we're doing is replacing the |
The error message is bad, it has nothing to do with logins. The file
You'll have to repeat this step after every plugin update and ideally after every system update because $NIX_CC can get garbage collected. |
Would it be possible to |
That sounds very annoying to be honest. I'd second the motion of @Krutonium to Nixify :) (Obviously I have no idea how much of a hassle that is, probably way more than I'd imagine) Thank you for the reply! |
Yep, that did it! Thanks! |
@Krutonium Have a look at #223593 |
Same bug in WebStorm. |
same in phpstorm |
Describe the bug
I'm unable to use the Copilot plugin in Rider as it won't let me log in and throws the following error:
"Failed to initiate the GitHub login process. Please try again."
Steps To Reproduce
Steps to reproduce the behavior:
I am following the steps as provided in the official documentation.
Expected behavior
I would expect it to open a webbrowser and let me connect the GitHub account to Rider.
Screenshots
Additional context
I can manually connect my GitHub account in the settings in Rider, but that is apparently not enough for the Copilot plugin.
Notify maintainers
@raphaelr
Metadata
The text was updated successfully, but these errors were encountered: