Adding Files as Context to Duo Chat Rollout Plan

Release Plan: Adding Project Files to Duo Chat

This release plan outlines the rollout of adding project files in Duo Chat for VS Code and JetBrains users on GitLab 17.7+

Prerequisites:

• ✅ Complete binary files handling: [LS] Binary files in context search results sho... (gitlab-org/editor-extensions/gitlab-lsp#471 - closed) • Elwyn Benson • 17.9 • On track
• Documentation updates
  • ✅ Include details on how to use the include comma... (!175490 - merged) • Dillon Wheeler, Ben Venker • 17.8
  • ✅ groupeditor extensions docs: add note about binary file support (!177696 - merged) • Elwyn Benson • 17.9.
  • ✅ Gitleaks documentation in review: !178333 (merged)
  • ✅ PLANNED FOR WEEK ENDING ON 17 JANUARY by groupeditor extensions. Further detail documentation, clarifying how files are treated that reside in projects that have rejected use of Duo.
    • Additional documentation not required since Duo Chat will not show up for project with Duo disabled.

Timeline:

✅ Phase 1: Internal Testing

• ✅ Enable feature for GitLab internal users
• ✅ Collect feedback and resolve critical issues
• ✅ Validate telemetry data collection via Tableau dashboard (https://10az.online.tableau.com/t/gitlab/views/AIGatewayReporting/Overview)

Phase 2: Documentation & Communication

• ✅ Finalize documentation: !175490 (diffs)
• ✅ Release post created: gitlab-com/www-gitlab-com!137718 (diffs). Will be merged in February, so it shows up in the release blog for %17.9
• ✅ Include the Feedback for include-file-context (#492443 - closed) issue in the release post

Phase 3: GA Release: 22 January on .com / 17.9 for SM

SM customers already have the ability to turn on the feature flags since SM %17.7. In %17.9 it will be on by default.

The following feature flag will need to be enabled for the .com release. SM customers can enable the feature flags for their own instance, but as the minimum version is 17.7, we won't see traffic from SM customers until they upgrade.

• [Feature flag] Enable duo_additional_context (#477503)
  • Controls access to additional context in Duo Chat
  • This feature flag will not affect the UI for end users
• [Feature flag] Rollout of `duo_include_context_... (#508741 - closed)
  • Controls access to include files

Non-Phased rollout

The following feature flag will be enabled on 20 January for .com in preparation for the phased rollout of the duo_incldue_context_file feature flag.

• [Feature flag] Enable duo_additional_context (#477503)
  • Controls access to additional context in Duo Chat
  • This feature flag will not affect the UI for end users

Phased rollout

The following feature flag will need to be enabled for the .com release. SM customers can enable the feature flags for their own instance, but as the minimum version is 17.7, we won't see traffic from SM customers until they upgrade.

• [Feature flag] Rollout of `duo_include_context_... (#508741 - closed)
  • Controls access to include files

DRI for the rollout: @dillonwheeler

Date	Interval for .com release	SM release	Status (Done or In Progress)	Continue or Revert?
Monday Jan 20, 2025	10%	Done	Done	Continue
	20%		Done	Continue
Tuesday Jan 21, 2025	30%	Don	Done	Continue
	50%		Done	Continue
Wednesday Jan 22, 2025	75%	Done	Done	Continue
	100%	Done	Done	Continue
Thursday Feb 20, 2025		Official 17.9 release	Done	Update duo chat include context ff (!181305 - merged)

Feature flag operators possibility for Follow-the-sun coverage:

• APAC: @shinya.maeda
• EMEA: @brytannia
• AMER: @dillonwheeler (Also updating the % rollout on each date outlined above)

Phase 4: Follow-up issues

• Fix this big UX issue: UX broken: one can add file(s) and then use ano... (#509344) • Unassigned • 18.6 groupeditor extensions

Phase 5: Blog post

• write a blog post about the benefits of the feature and how to use it: https://gitlab.com/gitlab-com/marketing/brand-product-marketing/content-strategy-and-ops/blog/-/issues/162+

Success Metrics:

1. Adoption: Track volume of requests that include added files as context
2. Usage: Monitor frequency of project file additions
3. Customer Satisfaction: Track feedback through dedicated issue
4. Performance: Monitor system impact

Rollback Strategy:

• Immediate feature flag disable capability
• Prepared user communication plan