48 lines
1.3 KiB
Markdown
48 lines
1.3 KiB
Markdown
---
|
|
type: system
|
|
project: fidelity
|
|
status: active
|
|
systems: []
|
|
workstreams: []
|
|
people: [jeff-dewitte]
|
|
related: []
|
|
tags:
|
|
- system
|
|
- fidelity
|
|
updated: 2026-04-20
|
|
---
|
|
|
|
# GitHub Copilot
|
|
|
|
## Role
|
|
|
|
- GitHub Copilot is a broadly used AI tool in the Fidelity workflow, especially when product-side code access and richer implementation context are available on the Fidelity machine.
|
|
|
|
---
|
|
|
|
## Stable Patterns
|
|
|
|
- Use this tool when the local Fidelity-side product context is richer than what can be summarized indirectly in chat.
|
|
- It is useful for investigation, code-oriented debugging, and implementation support when David can provide concrete build, file, and runtime details from the Fidelity development environment.
|
|
- Tool output should still be checked against local evidence, reproduction results, and confirmed project context.
|
|
|
|
---
|
|
|
|
## Current Example
|
|
|
|
- During the April 20, 2026 REST / LaunchDarkly investigation, Jeff specifically suggested using GitHub Copilot with more detailed local context from David's side.
|
|
|
|
---
|
|
|
|
## Risks
|
|
|
|
- Do not assume the tool output is authoritative without checking it against local evidence.
|
|
- Keep the tool's Fidelity-side access level and data visibility labeled as contextual rather than assumed workspace-wide.
|
|
|
|
---
|
|
|
|
## Related Context
|
|
|
|
- `project-knowledge/04-people/jeff-dewitte.md`
|
|
- `project-knowledge/02-work-items/pdiap-15838.md`
|