49 lines
1.5 KiB
Markdown
49 lines
1.5 KiB
Markdown
# Troubleshooting and FAQ
|
|
|
|
## Common Setup Issues
|
|
- Cannot sign in: confirm GitHub access and SSO.
|
|
- No suggestions: verify Copilot is enabled in the editor.
|
|
- Plugin missing: confirm the plugin or extension is installed.
|
|
|
|
### Example: No Suggestions
|
|
1. Confirm you are signed in.
|
|
2. Confirm the extension is enabled.
|
|
3. Open a new file and type a simple prompt.
|
|
4. Restart the editor if needed.
|
|
|
|
## Quick Diagnostic Flow
|
|
1. Confirm account access and SSO.
|
|
2. Confirm plugin or extension is installed and enabled.
|
|
3. Restart the editor.
|
|
4. Test with a small prompt in a new file.
|
|
5. If still blocked, escalate.
|
|
|
|
## Extension or Plugin Conflicts
|
|
- Disable overlapping AI extensions to avoid conflicts.
|
|
- Restart the editor after enabling Copilot.
|
|
|
|
## Company Network Restrictions
|
|
- Check for blocked endpoints or proxy requirements.
|
|
- Escalate to IT if access appears restricted.
|
|
|
|
## Low-Quality Suggestions
|
|
- Tighten the prompt with scope and context.
|
|
- Provide a small example or expected output.
|
|
|
|
### Example Fix
|
|
Bad: "Fix this."
|
|
Better: "Refactor this function to remove duplication. Keep behavior the same."
|
|
|
|
## What To Collect Before Escalation
|
|
- Editor version and plugin version.
|
|
- Error messages or screenshots.
|
|
- Whether the issue is reproducible in another editor.
|
|
|
|
### Example Escalation Note
|
|
"Copilot suggestions stopped in VS Code 1.92 after extension update. Restarted, still broken. Screenshot attached."
|
|
|
|
## When to Escalate
|
|
- Account access issues after setup.
|
|
- Consistent failures across multiple editors.
|
|
- Policy or security concerns.
|