From 051231d7e7ca389ab3427b17f53d02b9a4b03339 Mon Sep 17 00:00:00 2001 From: "codegen-sh[bot]" <131295404+codegen-sh[bot]@users.noreply.github.com> Date: Thu, 18 Sep 2025 12:44:15 +0000 Subject: [PATCH] Add multi-repo organization tips to FAQ - Added new FAQ section for users in organizations with multiple repositories - Covers repository access, discovery, and navigation best practices - Includes tips for team coordination and repository-specific configuration - Provides clear guidance for getting started with multi-repo workflows Co-authored-by: Edo Pujol --- docs/introduction/faq.mdx | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/docs/introduction/faq.mdx b/docs/introduction/faq.mdx index a2accd1de..09757ac49 100644 --- a/docs/introduction/faq.mdx +++ b/docs/introduction/faq.mdx @@ -53,4 +53,27 @@ iconType: "solid" issues](https://github.com/codegen-sh/codegen-sdk) for bug reports or SDK feature requests 3. Reach out to us on [Twitter](https://x.com/codegen) + + If your organization has multiple repositories, here are some tips to get started effectively: + + **Repository Access & Discovery:** + - Visit [codegen.com/repos](https://codegen.com/repos) to see all repositories you have access to + - Use the "Configure GitHub" button to manage repository permissions + - Codegen agents can work across any repository where the GitHub App is installed + + **Best Practices:** + - **Start Small**: Begin with 1-2 key repositories to get familiar with Codegen's workflow + - **Repository-Specific Rules**: Use [Repository Rules](/settings/repo-rules) to set coding standards and preferences for each repo + - **Clear Context**: When requesting work, specify which repository you want the agent to work on (e.g., "@codegen in the frontend repo, please...") + - **Team Coordination**: Use [Team Roles](/settings/team-roles) to manage access and permissions across your organization + + **Navigation Tips:** + - Agents automatically detect which repository context is needed based on your requests + - You can explicitly mention repository names in Slack, Linear, or API calls + - Repository settings and rules are inherited from your organization but can be customized per repo + + + For large organizations with many repositories, consider setting up organization-wide rules first, then customizing specific repositories as needed. + +