Robert Clover cbe7a12e65 Add information to Copilot sign-in UI when disabled (#7496) ... I'd love to take on fixing this but: 1. I don't think this is the right solution - it would be really nice to have something actionable that I could do when presented with this message. 2. Should signing in to Copilot be independent from whether it's enabled? You can only access the sign-in modal when `features.copilot` isn't disabled, but when `show_copilot_suggestions` is `false` the server is disabled but you can't sign in. So I guess another solution might be to just not show the UI if copilot suggestions are disabled? 3. I don't know what other circumstances could trigger the empty modal. I see `Status::Error` and that seems like it might be important to surface gracefully? Would love some thoughts on this Release Notes: - Improved UX for enabling Copilot when it's disabled in settings		2024-02-07 22:28:02 -07:00
..
src	Add information to Copilot sign-in UI when disabled (#7496)	2024-02-07 22:28:02 -07:00
Cargo.toml	chore: Move workspace dependencies to workspace.dependencies (#7454)	2024-02-06 20:41:36 +01:00
LICENSE-GPL	chore: Change AGPL-licensed crates to GPL (except for collab) (#4231)	2024-01-24 00:26:58 +01:00