## Summary This issue tracks the rollout of the Orbit-powered Code Intelligence side panel, currently behind the `orbit_code_intelligence` feature flag. The feature adds a **Code Intelligence** button to the blob file viewer. When enabled, it opens a side panel showing all symbols defined in the current file (with caller-count badges), and lets developers drill into any symbol to see its inbound references and outbound calls — powered by the Orbit knowledge graph, with zero CI configuration required. - Feature MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/234404 - KG schema MR: https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/merge_requests/1173 ## Owners - Most appropriate Slack channel to reach out to: `#g_knowledge_graph` - Best individual to reach out to: @phikai ## Expectations ### What are we expecting to happen? A "Code Intelligence" button appears in the blob header for all files in Orbit-indexed projects. Clicking it opens a sticky side panel with: - All definitions in the file sorted by type, with caller-count badges - Per-symbol detail view: references (who calls this?) and calls (what does this call?), grouped by file with line links ### What can go wrong and how would we detect it? - Orbit API queries fail or are slow → panel shows an alert, blob viewer is unaffected (panel is additive) - JS bundle errors → would appear in browser console; blob viewer itself should not be impacted as the component is lazy-loaded - No symbols shown for indexed files → check Orbit indexing status for the project ## Rollout Steps ### Rollout on non-production environments - [ ] Deploy the feature flag at a percentage with `/chatops gitlab run feature set orbit_code_intelligence <rollout-percentage> --actors --dev --pre --staging --staging-ref` - [ ] Monitor that the error rates did not increase. - [x] Enable the feature for internal users on non-production environments with `/chatops gitlab run feature set orbit_code_intelligence true --dev --pre --staging --staging-ref` - [x] Verify that the feature works as expected on staging-canary. ### Specific rollout on production - [ ] Enable for all internal GitLab team members first: `/chatops gitlab run feature set --feature-group=gitlab_team_members orbit_code_intelligence true` - [ ] Verify the feature works correctly for team members. - [ ] Incrementally roll out to broader production: `/chatops gitlab run feature set orbit_code_intelligence <rollout-percentage> --actors` ### Preparation before global rollout - [ ] Set a milestone to this issue to signal enabling and removing the feature flag. - [ ] Ensure documentation exists for the feature and version history text is updated. - [ ] Notify `#support_gitlab-com` and the team channel before global rollout. ### Global rollout on production - [ ] Incrementally roll out on production (50% → 100%), monitoring dashboards between steps. - [ ] After 100% enabled, wait at least one day before releasing. ## Rollback Steps - [ ] Disable on production: ``` /chatops gitlab run feature set orbit_code_intelligence false ``` - [ ] Disable on non-production environments: ``` /chatops gitlab run feature set orbit_code_intelligence false --dev --pre --staging --staging-ref ``` - [ ] Delete from all environments: ``` /chatops gitlab run feature delete orbit_code_intelligence --dev --pre --staging --staging-ref --production ```