[Feat] Support different / multiple GitHub credentials in different Eclipse workspaces
维护者通常 3 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 12/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- github-actions, java
调研方向
The request is about how the Copilot Eclipse plugin stores and switches GitHub credentials, so the entry points are the plugin's authentication and account-storage code, which the payload does not name. Read how the plugin persists its login today, then compare with how Eclipse Git handles per-repository authentication. Done would be a design decision on per-user versus per-workspace storage, which the maintainers have not yet made.
由索引模型根据 Issue 内容生成。
描述
Is your feature request related to a problem? Please describe.
As someone works on personal, open-source, business and client projects in Eclipse, I end up using different GitHub orgs and credentials (direct, enterprise, etc.). The GitHub co-pilot plugin does not support multiple GitHub authentications on the same machine. When switching between different types of work (workspaces), the only way to use the right GitHub CoPilot license with the right project is to log out of CoPilot and log back in, which is a pain when you are switching workspaces more than once a day.
Note: Eclipse Git supports different authentications for different repositories.
Describe the solution you'd like
In my opinion either one of the two solutions could work (first one preferred):
- Support multiple authentications in the GitHub Copilot Eclipse plugin, and allow switching between users easily. (Similar to how you can be logged into multiple users on github.com in a browser and switch users)
- Store copilot authorizations at the workspace level, rather than at the user profile (?) level. This allows different workspaces to automatically be logged into the 'right' GitHub account. The only drawback being having to log into the same credentials from different workspaces while working on the same GitHub org.
Describe alternatives you've considered
Some users online have suggested using different Eclipse installations for different orgs, which may not work very clean or manageable.
Additional context
None
- 主要语言
- Java
- 星标
- 128
- 派生
- 66
- 平均合并
- 1 天 22 小时
- 30 天内合并 PR
- 7
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
microsoft/copilot-for-eclipse 的其他 Issue
-
[Bug]未关闭bug
难度 2/5 1-3 小时 新手友好度 64/100
microsoft/copilot-for-eclipse#480 ·
维护者通常 3 天内回复
-
bug
难度 4/5 3-5 天 新手友好度 15/100
microsoft/copilot-for-eclipse#489 ·
维护者通常 3 天内回复
-
bug
难度 4/5 3-5 天 新手友好度 22/100
microsoft/copilot-for-eclipse#486 ·
维护者通常 3 天内回复
-
bug
难度 4/5 3-5 天 新手友好度 22/100
microsoft/copilot-for-eclipse#485 ·
维护者通常 3 天内回复
-
bug
难度 4/5 3-5 天 新手友好度 22/100
microsoft/copilot-for-eclipse#481 ·
维护者通常 3 天内回复
查看 microsoft/copilot-for-eclipse 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
bug new windows
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
GantMan/jail-monkey#380 ·
-
难度 2/5 1-3 小时 新手友好度 72/100
objectionary/jucs#145 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
objectionary/lints#1559 ·
维护者通常 2 天内回复