back_office_ops · security · workflow
1Password increases developer productivity across a distributed codebase with Sourcegraph Code Search and Cody
As 1Password's codebase expanded from two monorepos to more than 200 repositories across multiple GitHub and GitLab instances, developers struggled to find code they hadn't personally worked on and often had to ask colleagues via Slack.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Developer searches entire codebase
An engineer searches for code across the entire codebase and all code hosts from a single place.
Tools used
Code SearchCodySourcegraph
Outcome
Developers became self-sufficient in finding code across all repositories, while Cody reduced the toil of writing unit tests and making programmatic edits, collectively advancing 1Password's innersourcing initiative.
What failed first
The native code search tools built into GitHub and GitLab were limited to searching within each individual code host, making cross-host code discovery ineffective.
Results
Time savedsaved me a ton of time
Volumemore than 200 repositories
Source
https://sourcegraph.com/case-studies/1password-increases-productivity-in-a-distributed-codebase
Grounding & classification
Source type: vendor customer story
26 fields verified against source quotes.
code generationenterprise searchknowledge searchcode diff prknowledge basefailure mode describednamed customerproduction runtime claimedsource backedtools describedworkflow describedsoftwareemployee productivitytime savedvendor customer storyback office opsagentic task executionrag answering