diff --git a/autodev/architecture/webhook.mdx b/autodev/architecture/webhook.mdx deleted file mode 100644 index f6bdb34..0000000 --- a/autodev/architecture/webhook.mdx +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: "GitHub Webhook" -description: "Learn how AutoDev works with GitHub Webhook" ---- - - diff --git a/autodev/ai-agents/claude-code.mdx b/devbird/ai-agents/claude-code.mdx similarity index 68% rename from autodev/ai-agents/claude-code.mdx rename to devbird/ai-agents/claude-code.mdx index ea72ba7..39ff93a 100644 --- a/autodev/ai-agents/claude-code.mdx +++ b/devbird/ai-agents/claude-code.mdx @@ -1,20 +1,23 @@ --- title: "Claude Code" -description: "Setup and usage guide for Claude Code with AutoDev" +description: "Setup and usage guide for Claude Code with DevBird" --- -This guide covers connecting Claude Code to your repository. To set up AutoDev itself, please refer to the [AutoDev setup guide](/autodev/getting-started/prerequisites). + This guide covers connecting Claude Code to your repository. To set up DevBird + itself, please refer to the [DevBird setup + guide](/devbird/getting-started/prerequisites). -Claude Code is Anthropic's AI coding assistant. When integrated with AutoDev, it can automate code generation, bug fixes, refactoring, and more through natural language commands. +Claude Code is Anthropic's AI coding assistant. When integrated with DevBird, it can automate code generation, bug fixes, refactoring, and more through natural language commands. ## Prerequisites Before you begin, ensure you have: + - Claude Code installed on your machine - A Claude subscription (recommended for long-lived token option) -- Repository access where you want to use AutoDev +- Repository access where you want to use DevBird ## Setup Process @@ -26,6 +29,7 @@ Before you begin, ensure you have: ### Step 2: Install GitHub App 1. In the Claude Code terminal, run: + ```bash /install-github-app ``` @@ -34,11 +38,11 @@ Before you begin, ensure you have: ### Step 3: Select Repository -Select the repository where you want to use AutoDev from the list presented. +Select the repository where you want to use DevBird from the list presented. ### Step 4: Install GitHub App -Follow the GitHub prompts to install the AutoDev app to your selected repository. +Follow the GitHub prompts to install the DevBird app to your selected repository. ### Step 5: Configure Workflows @@ -49,6 +53,7 @@ When Claude Code displays the `Select GitHub workflows to install` screen, press Claude Code will present the `Install GitHub App` screen with authentication options: - **Create a long-lived token with your Claude subscription** (Recommended) + - Uses your existing Claude subscription (flat rate billing) - More cost-effective for regular use - Requires approval on the Anthropic website @@ -58,7 +63,8 @@ Claude Code will present the `Install GitHub App` screen with authentication opt - Charges based on usage -We recommend the long-lived token option if you have a Claude subscription, as it provides predictable costs. + We recommend the long-lived token option if you have a Claude subscription, as + it provides predictable costs. ### Step 7: Approve on Anthropic Website @@ -70,12 +76,11 @@ If you selected the long-lived token option, approve the connection on the Anthr Claude Code will automatically create a setup pull request in your repository: - **If you plan to use Claude Code directly**: Review and merge the PR -- **If you only plan to use AutoDev (without using Claude Code directly)**: You don't need this PR - you can close it without merging +- **If you only plan to use DevBird (without using Claude Code directly)**: You don't need this PR - you can close it without merging - **If you're just testing**: You can close the PR without merging ## Next Steps -- [Create your first PR](/autodev/getting-started/first-pr) -- [Unit Task Guide](/autodev/tasks/unit) -- [Composite Task Guide](/autodev/tasks/composite) - +- [Create your first PR](/devbird/getting-started/first-pr) +- [Unit Task Guide](/devbird/tasks/unit) +- [Composite Task Guide](/devbird/tasks/composite) diff --git a/autodev/ai-agents/codex-cli.mdx b/devbird/ai-agents/codex-cli.mdx similarity index 58% rename from autodev/ai-agents/codex-cli.mdx rename to devbird/ai-agents/codex-cli.mdx index c564110..4d177a6 100644 --- a/autodev/ai-agents/codex-cli.mdx +++ b/devbird/ai-agents/codex-cli.mdx @@ -1,19 +1,22 @@ --- title: "Codex CLI by OpenAI" -description: "Setup and usage guide for Codex CLI with AutoDev" +description: "Setup and usage guide for Codex CLI with DevBird" --- -This guide covers connecting Codex CLI to your repository. To set up AutoDev itself, please refer to the [AutoDev setup guide](/autodev/getting-started/prerequisites). + This guide covers connecting Codex CLI to your repository. To set up DevBird + itself, please refer to the [DevBird setup + guide](/devbird/getting-started/prerequisites). -Codex CLI is OpenAI's AI coding assistant. When integrated with AutoDev, it can automate code generation, bug fixes, refactoring, and more through natural language commands. +Codex CLI is OpenAI's AI coding assistant. When integrated with DevBird, it can automate code generation, bug fixes, refactoring, and more through natural language commands. ## Prerequisites Before you begin, ensure you have: + - An OpenAI account -- Repository access where you want to use AutoDev +- Repository access where you want to use DevBird ## Setup Process @@ -21,7 +24,7 @@ Before you begin, ensure you have: 1. Go to the [OpenAI API keys page](https://platform.openai.com/api-keys) 2. Click **Create new secret key** -3. Give your key a descriptive name (e.g., "AutoDev") +3. Give your key a descriptive name (e.g., "DevBird") 4. Copy the generated API key (you won't be able to see it again) ### Step 2: Add API Key to GitHub Repository @@ -35,6 +38,6 @@ Before you begin, ensure you have: ## Next Steps -- [Create your first PR](/autodev/getting-started/first-pr) -- [Unit Task Guide](/autodev/tasks/unit) -- [Composite Task Guide](/autodev/tasks/composite) +- [Create your first PR](/devbird/getting-started/first-pr) +- [Unit Task Guide](/devbird/tasks/unit) +- [Composite Task Guide](/devbird/tasks/composite) diff --git a/autodev/ai-agents/crush-cli.mdx b/devbird/ai-agents/crush-cli.mdx similarity index 100% rename from autodev/ai-agents/crush-cli.mdx rename to devbird/ai-agents/crush-cli.mdx diff --git a/autodev/ai-agents/gemini-cli.mdx b/devbird/ai-agents/gemini-cli.mdx similarity index 100% rename from autodev/ai-agents/gemini-cli.mdx rename to devbird/ai-agents/gemini-cli.mdx diff --git a/autodev/ai-agents/github-copilot-cli.mdx b/devbird/ai-agents/github-copilot-cli.mdx similarity index 100% rename from autodev/ai-agents/github-copilot-cli.mdx rename to devbird/ai-agents/github-copilot-cli.mdx diff --git a/autodev/ai-agents/opencode.mdx b/devbird/ai-agents/opencode.mdx similarity index 100% rename from autodev/ai-agents/opencode.mdx rename to devbird/ai-agents/opencode.mdx diff --git a/devbird/architecture/webhook.mdx b/devbird/architecture/webhook.mdx new file mode 100644 index 0000000..1c6509e --- /dev/null +++ b/devbird/architecture/webhook.mdx @@ -0,0 +1,4 @@ +--- +title: "GitHub Webhook" +description: "Learn how DevBird works with GitHub Webhook" +--- diff --git a/autodev/comparison.mdx b/devbird/comparison.mdx similarity index 88% rename from autodev/comparison.mdx rename to devbird/comparison.mdx index 9a0e609..ac17223 100644 --- a/autodev/comparison.mdx +++ b/devbird/comparison.mdx @@ -1,18 +1,18 @@ --- title: "Comparison with other tools" -description: "Compare AutoDev with Claude Code Web and Codex CLI to find the best tool for your workflow" +description: "Compare DevBird with Claude Code Web and Codex CLI to find the best tool for your workflow" --- ## Feature Comparison Here's how it compares to other popular web-based AI agents. -| Feature | AutoDev | Claude Code Web | Codex Web | +| Feature | DevBird | Claude Code Web | Codex Web | | ------------------------------------ | :-------------------------------------------------------: | :-------------: | :-----------: | | **AI environment** | | | | | - **Runs on** | GitHub Actions | Cloud | Cloud | | - **Using own device** | ✅ , via Custom Runner | ❌ | ❌ | -| - **Configuring** | [`autodev.yml`](/autodev/getting-started/github-workflow) | ✅ (No setup) | ✅ (No setup) | +| - **Configuring** | [`devbird.yml`](/devbird/getting-started/github-workflow) | ✅ (No setup) | ✅ (No setup) | | - **Customization** | ✅,via github actions | ❌ | ❌ | | **Iteration (Feedback loop)** | ✅, Semi-automated | Manual | Manual | | - **Automatic CI fix** | ✅ | ❌ | ❌ | diff --git a/autodev/cost-reduction/github-runner.mdx b/devbird/cost-reduction/github-runner.mdx similarity index 100% rename from autodev/cost-reduction/github-runner.mdx rename to devbird/cost-reduction/github-runner.mdx diff --git a/autodev/getting-started/ai-agent.mdx b/devbird/getting-started/ai-agent.mdx similarity index 57% rename from autodev/getting-started/ai-agent.mdx rename to devbird/getting-started/ai-agent.mdx index 448c10d..b0f9e08 100644 --- a/autodev/getting-started/ai-agent.mdx +++ b/devbird/getting-started/ai-agent.mdx @@ -1,26 +1,26 @@ --- title: "Configuring AI Agent" -description: "Learn how to configure AI agents for your AutoDev workflow" +description: "Learn how to configure AI agents for your DevBird workflow" --- -AutoDev supports multiple AI agent providers to power your development automation. Choose the right agent based on your use case and budget. +DevBird supports multiple AI agent providers to power your development automation. Choose the right agent based on your use case and budget. ## Supported AI Agents -You can configure the following AI agents in AutoDev: +You can configure the following AI agents in DevBird: -- [Claude Code](/autodev/ai-agents/claude-code) -- [Codex CLI](/autodev/ai-agents/codex-cli) -- [Crush CLI (WIP)](/autodev/ai-agents/crush-cli) -- [Gemini CLI (WIP)](/autodev/ai-agents/gemini-cli) -- [GitHub Copilot CLI (WIP)](/autodev/ai-agents/github-copilot-cli) -- [OpenCode (WIP)](/autodev/ai-agents/opencode) +- [Claude Code](/devbird/ai-agents/claude-code) +- [Codex CLI](/devbird/ai-agents/codex-cli) +- [Crush CLI (WIP)](/devbird/ai-agents/crush-cli) +- [Gemini CLI (WIP)](/devbird/ai-agents/gemini-cli) +- [GitHub Copilot CLI (WIP)](/devbird/ai-agents/github-copilot-cli) +- [OpenCode (WIP)](/devbird/ai-agents/opencode) ## Recommendations ### For Testing & Experimentation -If you're testing AutoDev or evaluating its capabilities, we recommend **OpenAI Codex with API Key** configuration: +If you're testing DevBird or evaluating its capabilities, we recommend **OpenAI Codex with API Key** configuration: - Quick setup with just an API key - Pay-per-use pricing @@ -29,7 +29,7 @@ If you're testing AutoDev or evaluating its capabilities, we recommend **OpenAI ### For Production Use -If you're serious about using AutoDev in your development workflow, we strongly recommend **Claude Code with Max Plan**: +If you're serious about using DevBird in your development workflow, we strongly recommend **Claude Code with Max Plan**: - Superior code understanding and generation - Best-in-class context handling @@ -39,5 +39,4 @@ If you're serious about using AutoDev in your development workflow, we strongly ## Using Multiple Agents -You can configure multiple AI agents in your GitHub repository. Once configured, you can select which agent to use for each task directly within the AutoDev app. - +You can configure multiple AI agents in your GitHub repository. Once configured, you can select which agent to use for each task directly within the DevBird app. diff --git a/autodev/getting-started/first-pr.mdx b/devbird/getting-started/first-pr.mdx similarity index 84% rename from autodev/getting-started/first-pr.mdx rename to devbird/getting-started/first-pr.mdx index ea0161c..de2351c 100644 --- a/autodev/getting-started/first-pr.mdx +++ b/devbird/getting-started/first-pr.mdx @@ -1,32 +1,34 @@ --- title: "Creating Your First PR" -description: "Step-by-step guide to creating your first AI-generated pull request with AutoDev" +description: "Step-by-step guide to creating your first AI-generated pull request with DevBird" --- -This guide walks you through creating your first pull request with AutoDev. +This guide walks you through creating your first pull request with DevBird. ## Prerequisites Before starting, ensure you've completed: -1. ✅ [Prerequisites](/autodev/getting-started/prerequisites) -2. ✅ [GitHub App Installation](/autodev/getting-started/github-app) -3. ✅ [GitHub Workflow Setup](/autodev/getting-started/github-workflow) -4. ✅ [AI Agent Configuration](/autodev/getting-started/ai-agent) -## Step 1: Access AutoDev Dashboard +1. ✅ [Prerequisites](/devbird/getting-started/prerequisites) +2. ✅ [GitHub App Installation](/devbird/getting-started/github-app) +3. ✅ [GitHub Workflow Setup](/devbird/getting-started/github-workflow) +4. ✅ [AI Agent Configuration](/devbird/getting-started/ai-agent) + +## Step 1: Access DevBird Dashboard 1. Go to [app.delino.io](https://app.delino.io) 2. Select your team from the team switcher -3. Navigate to the AutoDev section +3. Navigate to the DevBird section 4. You'll see the task creation form ## Step 2: Select Your Repository 1. Click the **Repository** dropdown 2. Select the repository where you want to create a PR -3. Only repositories with the AutoDev GitHub App installed will appear +3. Only repositories with the DevBird GitHub App installed will appear **Troubleshooting**: If your repository doesn't appear: + - Verify GitHub App installation - Check repository permissions - Refresh the page @@ -36,6 +38,7 @@ Before starting, ensure you've completed: Start with a simple, well-defined task for your first PR: ### Example 1: Bug Fix + ``` Fix the authentication bug where users get a 500 error when logging in with an empty email field. Add proper @@ -43,6 +46,7 @@ validation and return a 400 error with helpful message. ``` ### Example 2: Small Feature + ``` Add a dark mode toggle button to the settings page. Store the preference in localStorage and apply the @@ -50,6 +54,7 @@ theme across all pages. ``` ### Example 3: Refactoring + ``` Refactor the payment processing service to use async/await instead of callbacks. Update all related functions in @@ -57,6 +62,7 @@ instead of callbacks. Update all related functions in ``` **Tips for good prompts:** + - Be specific about what to fix or build - Include file paths using `@` notation - Mention technical requirements @@ -65,6 +71,7 @@ instead of callbacks. Update all related functions in ## Step 4: Configure Task Settings ### Task Type + For your first PR, **leave "Create as Composite Task" unchecked**. This creates a simple unit task, perfect for getting started. @@ -72,14 +79,17 @@ This creates a simple unit task, perfect for getting started. ### Advanced Settings (Optional) **AI Agent**: + - Leave blank to use your team's default - Or select a specific agent (e.g., "Claude Code") **Model Version**: + - Leave blank to use the agent's default - Or specify a model (e.g., "sonnet", "gpt-4") **Base Branch**: + - Leave blank to use the repository's default branch - Or specify a branch (e.g., "develop", "staging") @@ -95,17 +105,20 @@ This creates a simple unit task, perfect for getting started. The task details page shows: ### Initial Status: Pending + - Task is created and queued - GitHub Actions workflow is being triggered - Usually completes in seconds ### Status: In Progress + - AI agent is analyzing your request - Code is being written - Pull requests are being created - This can take 2-10 minutes depending on complexity ### Status: Completed + - All work is done - Pull requests have been created - Ready for review @@ -124,18 +137,21 @@ Once completed: ### What to expect **On GitHub PR page:** -- AutoDev task link comment + +- DevBird task link comment - Task prompt comment (shows what AI was asked to do) - Code changes in files - Automated tests running (CI checks) **Good signs:** + - Code follows your project's style - Tests are passing - Changes are focused and relevant - Documentation is updated if needed **Red flags:** + - Code doesn't compile - Tests are failing - Changes are unrelated to the task @@ -146,17 +162,19 @@ Once completed: If changes are needed: ### Option 1: GitHub Review Comments + 1. Leave review comments on the PR 2. Click "Request changes" or "Comment" -3. AutoDev automatically detects the review +3. DevBird automatically detects the review 4. AI agent makes updates based on your feedback 5. PR is updated with new changes ### Option 2: Manual Update Request + 1. Go to task details page 2. Click **Update PR** 3. Enter update instructions -4. AutoDev triggers update workflow +4. DevBird triggers update workflow 5. PR is updated with changes ## Step 9: Merge the PR @@ -171,13 +189,16 @@ When you're satisfied: ## Common First-Time Issues -### AutoDev not responding to reviews +### DevBird not responding to reviews + **Causes**: -- `autodev.yml` file missing or incorrect + +- `devbird.yml` file missing or incorrect - Agent not configured or API key missing **Solution**: -- Verify workflow file exists at `.github/workflows/autodev.yml` + +- Verify workflow file exists at `.github/workflows/devbird.yml` - Check file contents match the setup guide - Ensure workflow has correct permissions - Verify AI agent is set up correctly @@ -185,18 +206,22 @@ When you're satisfied: - Review agent configuration guide ### PR not created + **Cause**: Task completed but no branches were needed **Solution**: + - Check task prompt - was it clear what to create? - Review workflow execution logs - Task may have determined no changes were needed ### CI checks failing + **Cause**: Generated code has issues **Solution**: -- AutoDev automatically tries to fix CI failures + +- DevBird automatically tries to fix CI failures - Wait for auto-fix workflow to complete - If it fails again, add review comments with guidance @@ -205,18 +230,22 @@ When you're satisfied: Now that you've created your first PR: ### Try more complex tasks -- [Unit Tasks Guide](/autodev/tasks/unit) -- [Composite Tasks Guide](/autodev/tasks/composite) + +- [Unit Tasks Guide](/devbird/tasks/unit) +- [Composite Tasks Guide](/devbird/tasks/composite) ### Learn about PR management -- [PR Review Process](/autodev/reviewing-prs) -- [Settings Configuration](/autodev/settings) + +- [PR Review Process](/devbird/reviewing-prs) +- [Settings Configuration](/devbird/settings) ### Optimize your workflow -- [AI Agent Configuration](/autodev/ai-agents/claude-code) -- [Troubleshooting Guide](/autodev/troubleshooting/unit-task) + +- [AI Agent Configuration](/devbird/ai-agents/claude-code) +- [Troubleshooting Guide](/devbird/troubleshooting/unit-task) ### Advanced features + - Try creating a composite task for complex projects - Enable auto-approval for trusted workflows - Configure custom CI fix strategies @@ -224,26 +253,31 @@ Now that you've created your first PR: ## Tips for Success ### Start simple + - Begin with small, well-defined tasks - Learn how the AI interprets your prompts - Gradually increase complexity ### Iterate on prompts + - Refine your prompt writing based on results - Be more specific if output is too broad - Add constraints for better control ### Review carefully + - Always review AI-generated code - Don't merge without understanding changes - Treat it like code from a junior developer ### Collaborate with AI -- Use AutoDev for repetitive tasks + +- Use DevBird for repetitive tasks - Let it handle boilerplate code - Focus your time on complex logic and architecture ### Provide feedback + - Review comments help the AI improve - Be specific about what's wrong - Guide the AI toward better solutions @@ -253,6 +287,7 @@ Now that you've created your first PR: Let's walk through a complete example: **Prompt:** + ``` Add input validation to the user registration form. Email must be valid format, password must be at least @@ -260,6 +295,7 @@ Email must be valid format, password must be at least ``` **What happens:** + 1. Task created with auto-generated title: "Add input validation to user registration form" 2. GitHub Actions workflow triggered 3. AI agent analyzes the codebase @@ -270,22 +306,25 @@ Email must be valid format, password must be at least 8. Creates PR with all changes **Expected PR:** + - Frontend: Validation logic in registration component - Frontend: Error message UI components - Tests: Validation test cases - Total: ~100-200 lines across 3-4 files **Review:** + 1. Check validation logic is correct 2. Verify error messages are user-friendly 3. Ensure tests cover edge cases 4. Confirm no breaking changes **Result:** + - PR merged - Feature deployed - Task completed **Time saved:** ~1-2 hours of development work -You're now ready to use AutoDev for your development tasks! +You're now ready to use DevBird for your development tasks! diff --git a/autodev/getting-started/github-app.mdx b/devbird/getting-started/github-app.mdx similarity index 61% rename from autodev/getting-started/github-app.mdx rename to devbird/getting-started/github-app.mdx index d6cb8c4..a2838e1 100644 --- a/autodev/getting-started/github-app.mdx +++ b/devbird/getting-started/github-app.mdx @@ -1,22 +1,23 @@ --- title: "Installing GitHub App" -description: "Connect your GitHub repositories to AutoDev by installing the GitHub App" +description: "Connect your GitHub repositories to DevBird by installing the GitHub App" --- ## Prerequisites Before you begin, ensure you have: -- An active AutoDev account + +- An active DevBird account - Admin access to the GitHub organization or repository you want to connect - A GitHub account linked to your organization ## Installing the GitHub App -Follow these steps to connect your GitHub repositories to AutoDev: +Follow these steps to connect your GitHub repositories to DevBird: ### 1. Navigate to Repositories -In the AutoDev app, select the **Repositories** menu from the navigation. +In the DevBird app, select the **Repositories** menu from the navigation. ### 2. Connect your GitHub account @@ -27,14 +28,15 @@ Click on the option to connect your GitHub account. You'll be redirected to GitH Click **Install GitHub App** to begin the installation process. When prompted to select repositories: + - We recommend selecting **Only select repositories** -- Choose only the repositories you plan to use with AutoDev +- Choose only the repositories you plan to use with DevBird - This limits the app's access to only what you need -### 4. Connect repositories in AutoDev +### 4. Connect repositories in DevBird -After installation, return to the AutoDev app and select the repositories you want to use from the list of available repositories. +After installation, return to the DevBird app and select the repositories you want to use from the list of available repositories. ## Next steps -Once you've connected your repositories, you can start using AutoDev to automate your development workflow. +Once you've connected your repositories, you can start using DevBird to automate your development workflow. diff --git a/autodev/getting-started/github-workflow.mdx b/devbird/getting-started/github-workflow.mdx similarity index 58% rename from autodev/getting-started/github-workflow.mdx rename to devbird/getting-started/github-workflow.mdx index 6200168..0710392 100644 --- a/autodev/getting-started/github-workflow.mdx +++ b/devbird/getting-started/github-workflow.mdx @@ -1,36 +1,43 @@ --- title: "Adding GitHub Workflow" -description: "Set up the AutoDev GitHub Workflow in your repository to automate development tasks" +description: "Set up the DevBird GitHub Workflow in your repository to automate development tasks" --- + + Recently `autodev.yml` is renamed to `devbird.yml` because the product is + rebranded. But for backward compatibility, `autodev.yml` will just work as + before. + + ## Prerequisites Before you begin, ensure you have: -- Completed the [GitHub App installation](/autodev/getting-started/github-app) + +- Completed the [GitHub App installation](/devbird/getting-started/github-app) - Admin or write access to your repository - Required secrets configured in your GitHub repository ## Setting up the workflow -Follow these steps to add the AutoDev workflow to your repository: +Follow these steps to add the DevBird workflow to your repository: ### 1. Create the workflow file -Create a new file at `.github/workflows/autodev.yml` in your repository. +Create a new file at `.github/workflows/devbird.yml` in your repository. ### 2. Add the workflow configuration Copy the following YAML configuration into the file: ```yaml -name: 'AutoDev' -run-name: 'AutoDev: ${{ inputs.task_title }}' +name: "DevBird" +run-name: "DevBird: ${{ inputs.task_title }}" on: workflow_dispatch: inputs: prompt: - description: "Instructions for AutoDev. Can be a direct prompt or custom template." + description: "Instructions for DevBird. Can be a direct prompt or custom template." type: string required: true @@ -38,49 +45,48 @@ on: description: "The branch to use as the base/source when creating new branches (defaults to repository default branch)" type: string required: false - default: 'main' + default: "main" agent: - description: "The agent to use for the action. Can be 'claude_code', 'gemini_cli', 'codex_cli' or 'opencode'" - type: choice - default: 'claude_code' - options: - - claude_code - - gemini_cli - - codex_cli - - opencode - - crush_cli - - github_copilot_cli + description: "The agent to use for the action. Can be 'claude_code', 'gemini_cli', 'codex_cli' or 'opencode'" + type: choice + default: "claude_code" + options: + - claude_code + - gemini_cli + - codex_cli + - opencode + - crush_cli + - github_copilot_cli agent_model: description: "The (optional) model to use for the agent" type: string required: false - default: '' - + default: "" - autodev_workflow_execution_token: - description: "The token to use for the AutoDev task" + devbird_workflow_execution_token: + description: "The token to use for the DevBird task" type: string required: false - default: '' + default: "" - autodev_mode: - description: "The AutoDev execution mode. Can be 'develop' (default) or 'plan' (for task graph planning)" + devbird_mode: + description: "The DevBird execution mode. Can be 'develop' (default) or 'plan' (for task graph planning)" type: choice - default: 'develop' + default: "develop" options: - develop - plan task_title: - description: "The title of the AutoDev task" + description: "The title of the DevBird task" type: string required: false - default: '' + default: "" jobs: - autodev: + devbird: runs-on: ubuntu-latest permissions: contents: write @@ -97,13 +103,13 @@ jobs: # - name: Setup Node.js # uses: actions/setup-node - - name: Run AutoDev - uses: delinoio/autodev-action@main + - name: Run DevBird + uses: delinoio/devbird-action@main with: agent: ${{ inputs.agent }} agent_model: ${{ inputs.agent_model }} - autodev_mode: ${{ inputs.autodev_mode }} - autodev_workflow_execution_token: ${{ inputs.autodev_workflow_execution_token }} + devbird_mode: ${{ inputs.devbird_mode }} + devbird_workflow_execution_token: ${{ inputs.devbird_workflow_execution_token }} prompt: ${{ inputs.prompt }} base_branch: ${{ inputs.base_branch }} delino_access_token: ${{ secrets.DELINO_ACCESS_TOKEN }} @@ -126,14 +132,13 @@ Replace these with your project's setup steps. The steps here should configure a For example, the Delino monorepo includes steps for - - installing protoc for RPC definitions - - installing golang for backend servers - - installing nodejs for next.js apps - - fetching environment variables for development environment +- installing protoc for RPC definitions +- installing golang for backend servers +- installing nodejs for next.js apps +- fetching environment variables for development environment - ### 4. Configure `DELINO_ACCESS_TOKEN` Create a new API key following the guide at [Creating API Keys](/core/api-keys/creation) and add it as a repository secret on GitHub settings. @@ -143,11 +148,11 @@ Create a new API key following the guide at [Creating API Keys](/core/api-keys/c Commit the workflow file to your repository's main branch: ```bash -git add .github/workflows/autodev.yml -git commit -m "Add AutoDev workflow" +git add .github/workflows/devbird.yml +git commit -m "Add DevBird workflow" git push ``` ## Next steps -Once the workflow is set up, you can start using AutoDev to automate development tasks. Learn how to trigger your first AutoDev task in the [Creating your first PR](/autodev/getting-started/first-pr) guide. +Once the workflow is set up, you can start using DevBird to automate development tasks. Learn how to trigger your first DevBird task in the [Creating your first PR](/devbird/getting-started/first-pr) guide. diff --git a/autodev/getting-started/prerequisites.mdx b/devbird/getting-started/prerequisites.mdx similarity index 64% rename from autodev/getting-started/prerequisites.mdx rename to devbird/getting-started/prerequisites.mdx index e4e36d0..ed4efad 100644 --- a/autodev/getting-started/prerequisites.mdx +++ b/devbird/getting-started/prerequisites.mdx @@ -1,15 +1,15 @@ --- title: "Prerequisites" -description: "Requirements to get started with AutoDev" +description: "Requirements to get started with DevBird" --- -Before you begin using AutoDev, ensure you have the following: +Before you begin using DevBird, ensure you have the following: ## Delino Account -You need either a **Delino Pro** or **Delino Team** account to use AutoDev. +You need either a **Delino Pro** or **Delino Team** account to use DevBird. -The pricing of AutoDev is **\$0.01 per workflow execution, with a minimum charge of \$10 per month**. +The pricing of DevBird is **\$0.01 per workflow execution, with a minimum charge of \$10 per month**. Both plans offer the same features: @@ -18,9 +18,9 @@ Both plans offer the same features: ## GitHub Repository -AutoDev requires a GitHub repository to work with. Both public and private repositories are supported. +DevBird requires a GitHub repository to work with. Both public and private repositories are supported. -You'll need to install the GitHub App and grant AutoDev access to your repositories. See [Installing GitHub App](./github-app) for detailed instructions. +You'll need to install the GitHub App and grant DevBird access to your repositories. See [Installing GitHub App](./github-app) for detailed instructions. ## Next steps diff --git a/autodev/index.mdx b/devbird/index.mdx similarity index 56% rename from autodev/index.mdx rename to devbird/index.mdx index 59eb2a1..fce790d 100644 --- a/autodev/index.mdx +++ b/devbird/index.mdx @@ -1,38 +1,42 @@ --- -title: "What is AutoDev?" +title: "What is DevBird?" description: "AI-powered automated development platform that creates and manages pull requests" --- -AutoDev is a fully automated development platform that uses AI coding agents to handle development tasks end-to-end. Instead of manually writing code, you describe what you need, and AutoDev's AI agents create pull requests, respond to code reviews, and fix CI failures automatically. +DevBird is a fully automated development platform that uses AI coding agents to handle development tasks end-to-end. Instead of manually writing code, you describe what you need, and DevBird's AI agents create pull requests, respond to code reviews, and fix CI failures automatically. ## How it works -1. **Connect your repository** - Install the AutoDev GitHub App on your repositories -2. **Describe your task** - Tell AutoDev what you want to build or fix -3. **AI creates PRs** - AutoDev's AI agents write code and create pull requests -4. **Automatic management** - AutoDev responds to reviews and fixes CI failures +1. **Connect your repository** - Install the DevBird GitHub App on your repositories +2. **Describe your task** - Tell DevBird what you want to build or fix +3. **AI creates PRs** - DevBird's AI agents write code and create pull requests +4. **Automatic management** - DevBird responds to reviews and fixes CI failures 5. **You review and merge** - Review the AI-generated code and merge when ready ## Key features ### Simple tasks -Perfect for straightforward development work like bug fixes, small features, or refactoring. AutoDev creates one or more pull requests to complete your task. + +Perfect for straightforward development work like bug fixes, small features, or refactoring. DevBird creates one or more pull requests to complete your task. ### Composite tasks -For complex projects, AutoDev breaks down your request into multiple coordinated tasks with AI-powered planning. Each task builds on previous work, creating a complete solution step by step. + +For complex projects, DevBird breaks down your request into multiple coordinated tasks with AI-powered planning. Each task builds on previous work, creating a complete solution step by step. ### Automated PR management + - Responds to code review comments automatically - Fixes failing CI checks without manual intervention - Converts PRs to draft during updates to avoid confusion - Posts task context as comments for reviewers ### Multiple AI agents -Choose from [supported AI coding agents](/autodev/getting-started/ai-agent). + +Choose from [supported AI coding agents](/devbird/getting-started/ai-agent). ## Use cases -- **Bug fixes** - Describe the bug and AutoDev creates a fix +- **Bug fixes** - Describe the bug and DevBird creates a fix - **New features** - Request a feature and get a complete implementation - **Refactoring** - Improve code quality with automated refactoring - **Documentation** - Generate or update documentation automatically @@ -41,10 +45,10 @@ Choose from [supported AI coding agents](/autodev/getting-started/ai-agent). ## Getting started -Follow the setup guide to start using AutoDev: +Follow the setup guide to start using DevBird: -1. [Prerequisites](/autodev/getting-started/prerequisites) - What you need before starting -2. [Install GitHub App](/autodev/getting-started/github-app) - Connect AutoDev to your repositories -3. [Set up workflow](/autodev/getting-started/github-workflow) - Add the AutoDev workflow to your repository -4. [Configure AI agent](/autodev/getting-started/ai-agent) - Set up your preferred AI coding agent -5. [Create your first PR](/autodev/getting-started/first-pr) - Generate your first AI-powered pull request +1. [Prerequisites](/devbird/getting-started/prerequisites) - What you need before starting +2. [Install GitHub App](/devbird/getting-started/github-app) - Connect DevBird to your repositories +3. [Set up workflow](/devbird/getting-started/github-workflow) - Add the DevBird workflow to your repository +4. [Configure AI agent](/devbird/getting-started/ai-agent) - Set up your preferred AI coding agent +5. [Create your first PR](/devbird/getting-started/first-pr) - Generate your first AI-powered pull request diff --git a/autodev/reviewing-prs/ai-reviewer.mdx b/devbird/reviewing-prs/ai-reviewer.mdx similarity index 79% rename from autodev/reviewing-prs/ai-reviewer.mdx rename to devbird/reviewing-prs/ai-reviewer.mdx index 67f6327..c1f651f 100644 --- a/autodev/reviewing-prs/ai-reviewer.mdx +++ b/devbird/reviewing-prs/ai-reviewer.mdx @@ -3,36 +3,40 @@ title: "Configuring AI Reviewer" description: "Enable bot reviews and automated code quality checks" --- -AutoDev can automatically respond to reviews from bot accounts, enabling automated code quality workflows. +DevBird can automatically respond to reviews from bot accounts, enabling automated code quality workflows. ## What is Auto-Apply Bot Reviews? -AutoDev can automatically respond to reviews from bot accounts. For detailed information about this setting including how to enable it, when to use it, and configuration options, see the [Auto-apply Bot Reviews](/autodev/settings#auto-apply-bot-reviews) documentation. +DevBird can automatically respond to reviews from bot accounts. For detailed information about this setting including how to enable it, when to use it, and configuration options, see the [Auto-apply Bot Reviews](/devbird/settings#auto-apply-bot-reviews) documentation. ## How It Works ### Normal Review Workflow **Without auto-apply:** + 1. Bot submits review 2. Nothing happens (bot hasn't connected repository) 3. Review is ignored **With auto-apply enabled:** + 1. Bot submits review -2. AutoDev detects it's a bot account +2. DevBird detects it's a bot account 3. Automatically triggers update workflow 4. Uses GitHub App credentials 5. PR is updated based on bot feedback ### Bot Detection -AutoDev identifies bots using GitHub's API: +DevBird identifies bots using GitHub's API: + - Checks reviewer's `type` field - `type: "Bot"` = automated account - `type: "User"` = human account Common bot accounts: + - Dependabot - Renovate - CodeClimate @@ -41,13 +45,14 @@ Common bot accounts: ## Use Cases -For common use cases including code quality bots, security scanning, and dependency updates, see the [Auto-apply Bot Reviews use cases](/autodev/settings#auto-apply-bot-reviews) in the settings documentation. +For common use cases including code quality bots, security scanning, and dependency updates, see the [Auto-apply Bot Reviews use cases](/devbird/settings#auto-apply-bot-reviews) in the settings documentation. ## Configuration ### Team-Level Setting Auto-apply is configured per team: + - All team members use same setting - Applies to all connected repositories - Can be toggled on/off anytime @@ -58,32 +63,35 @@ Currently, the setting applies to all repositories in the team. Future versions ## Disabling Auto-Apply -For information about when and how to disable this feature, see [when to disable Auto-apply Bot Reviews](/autodev/settings#auto-apply-bot-reviews) in the settings documentation. +For information about when and how to disable this feature, see [when to disable Auto-apply Bot Reviews](/devbird/settings#auto-apply-bot-reviews) in the settings documentation. ## Troubleshooting -For detailed troubleshooting of bot reviews and auto-apply issues, see the [AI Reviewer Troubleshooting](/autodev/troubleshooting/ai-reviewer) guide. +For detailed troubleshooting of bot reviews and auto-apply issues, see the [AI Reviewer Troubleshooting](/devbird/troubleshooting/ai-reviewer) guide. ## Best Practices -For best practices and configuration recommendations, see the [Auto-apply Bot Reviews configuration tips](/autodev/settings#configuration-tips) in the settings documentation. +For best practices and configuration recommendations, see the [Auto-apply Bot Reviews configuration tips](/devbird/settings#configuration-tips) in the settings documentation. ## Supported Bot Platforms -AutoDev auto-apply works with any bot account recognized by GitHub: +DevBird auto-apply works with any bot account recognized by GitHub: **Dependency Management:** + - Dependabot - Renovate - Greenkeeper **Code Quality:** + - CodeClimate - SonarCloud - Codacy - DeepSource **Custom Bots:** + - Any bot created with GitHub App - Custom CI/CD bots - Internal automation tools @@ -93,10 +101,12 @@ AutoDev auto-apply works with any bot account recognized by GitHub: ### Current Limitations 1. **Team-level only:** + - Cannot configure per-repository - All repos use team setting 2. **All-or-nothing:** + - Cannot select specific bots - Either all bots or no bots @@ -107,6 +117,7 @@ AutoDev auto-apply works with any bot account recognized by GitHub: ### Future Enhancements Planned features: + - Per-repository settings - Bot allowlist/blocklist - Conditional auto-apply rules @@ -138,11 +149,11 @@ You can also manually apply bot review feedback from other PRs using the Reflect 2. Submit a review with "Request changes" on the current PR 3. Use the Reflect command with the comment URL -This allows you to selectively apply bot reviews without enabling auto-apply. For detailed instructions, see [Applying reviews from other PRs](/autodev/reviewing-prs#applying-reviews-from-other-prs). +This allows you to selectively apply bot reviews without enabling auto-apply. For detailed instructions, see [Applying reviews from other PRs](/devbird/reviewing-prs#applying-reviews-from-other-prs). ## Next Steps -- [AI Reviewer Troubleshooting](/autodev/troubleshooting/ai-reviewer) -- [PR Review Process](/autodev/reviewing-prs) -- [Settings Configuration](/autodev/settings) -- [Unit Task Guide](/autodev/tasks/unit) +- [AI Reviewer Troubleshooting](/devbird/troubleshooting/ai-reviewer) +- [PR Review Process](/devbird/reviewing-prs) +- [Settings Configuration](/devbird/settings) +- [Unit Task Guide](/devbird/tasks/unit) diff --git a/autodev/reviewing-prs/index.mdx b/devbird/reviewing-prs/index.mdx similarity index 74% rename from autodev/reviewing-prs/index.mdx rename to devbird/reviewing-prs/index.mdx index 888deba..70cc05f 100644 --- a/autodev/reviewing-prs/index.mdx +++ b/devbird/reviewing-prs/index.mdx @@ -1,27 +1,33 @@ --- -title: "How AutoDev Handles PR Reviews" -description: "Understand AutoDev's automated pull request review and update workflow" +title: "How DevBird Handles PR Reviews" +description: "Understand DevBird's automated pull request review and update workflow" --- -AutoDev automatically manages pull request reviews and updates, responding to feedback and fixing issues without manual intervention. +DevBird automatically manages pull request reviews and updates, responding to feedback and fixing issues without manual intervention. ## The automated PR workflow ### 1. PR Creation -When AutoDev creates a pull request: + +When DevBird creates a pull request: + - PR is opened for review - Task link comment is added - Task prompt comment is added (if enabled) - CI checks begin running ### 2. Code Review + Team members review the PR normally: + - Leave review comments - Request changes - Approve changes ### 3. Automatic Response -When a review is submitted, AutoDev: + +When a review is submitted, DevBird: + - Detects the review via GitHub webhook - Converts PR to draft status (except for simple approvals) - Triggers a workflow to address the feedback @@ -30,7 +36,9 @@ When a review is submitted, AutoDev: - CI checks run again ### 4. CI Monitoring -AutoDev watches CI check status: + +DevBird watches CI check status: + - When all checks complete - If any checks fail - Automatically triggers fix workflow @@ -38,7 +46,9 @@ AutoDev watches CI check status: - Updates are pushed to the PR ### 5. Ready for Merge + When everything passes: + - All CI checks pass - All review feedback addressed - PR is automatically undrafted (if enabled) @@ -47,86 +57,104 @@ When everything passes: ## PR comments ### Task Link Comment -Always added to every AutoDev PR: + +Always added to every DevBird PR: ```markdown -🤖 This pull request has been linked to AutoDev Task #123 +🤖 This pull request has been linked to DevBird Task #123 View the task details and manage the automated development -workflow in AutoDev. +workflow in DevBird. ``` Provides: -- Link to the AutoDev task + +- Link to the DevBird task - Task ID reference - Context for reviewers ### Task Prompt Comment + Optional, enabled by default. Shows the original task prompt in PR comments to provide context for reviewers. -For details about this feature including benefits and how to configure it, see [Enable Prompt Comments](/autodev/settings#enable-prompt-comments) in the settings documentation. +For details about this feature including benefits and how to configure it, see [Enable Prompt Comments](/devbird/settings#enable-prompt-comments) in the settings documentation. ## Review types and behavior ### Changes Requested + When reviewer requests changes: + 1. PR converts to draft -2. AutoDev workflow triggered +2. DevBird workflow triggered 3. AI analyzes review comments 4. Changes are made and pushed 5. PR remains draft until CI passes ### Comments Only + When reviewer adds comments (not requesting changes): + 1. PR converts to draft -2. AutoDev workflow triggered +2. DevBird workflow triggered 3. AI addresses comments 4. Updates pushed to PR 5. PR remains draft until CI passes ### Approvals + When reviewer approves without comments: + 1. PR stays as-is (not converted to draft) 2. No workflow triggered 3. PR ready for merge (if CI passes) ### Bot Reviews -When a bot account submits a review, behavior depends on the "Auto-apply Bot Reviews" setting. See [Settings](/autodev/settings) for details. + +When a bot account submits a review, behavior depends on the "Auto-apply Bot Reviews" setting. See [Settings](/devbird/settings) for details. ## Reviewer permissions -For security, AutoDev verifies that reviewers have appropriate permissions before triggering workflows: +For security, DevBird verifies that reviewers have appropriate permissions before triggering workflows: ### Write Access Requirement + **For human reviewers:** + - Must have **Write** (Push) or **Admin** access to the repository - Verified via GitHub API permission check - Reviews from users without write access are silently ignored - All permission checks are logged for security auditing **For bot reviewers:** + - Exempt from permission checks when "Auto-apply Bot Reviews" is enabled - Use GitHub App installation token for authentication - Bypasses individual permission requirements ### Why write access is required + This security measure prevents: + - Unauthorized users from triggering workflows via PR reviews - Potential abuse of compute resources - Unauthorized code execution in your workflows ### Troubleshooting permission issues + If your reviews aren't triggering workflows: + 1. Verify you have **Write** or **Admin** access to the repository -2. Check that you've connected the repository in AutoDev -3. Ensure the repository has AutoDev webhook configured +2. Check that you've connected the repository in DevBird +3. Ensure the repository has DevBird webhook configured 4. Review webhook delivery logs for permission errors -**Note**: Read-only collaborators cannot trigger AutoDev workflows through PR reviews, even if they've connected the repository. +**Note**: Read-only collaborators cannot trigger DevBird workflows through PR reviews, even if they've connected the repository. ## Draft status during updates -AutoDev converts PRs to draft during automated updates to: +DevBird converts PRs to draft during automated updates to: + - Signal work is in progress - Prevent accidental merges during changes - Avoid confusing reviewers @@ -139,14 +167,18 @@ AutoDev converts PRs to draft during automated updates to: When CI checks fail: ### Detection -AutoDev monitors: + +DevBird monitors: + - `check_run` webhooks - `check_suite` webhooks - Waits for all checks to complete - Identifies failing checks ### Fix Workflow + If failures detected: + 1. Creates fix workflow execution 2. Converts PR to draft 3. Generates detailed fix prompt with: @@ -158,65 +190,75 @@ If failures detected: 6. CI runs again ### Rate Limiting + To prevent excessive fix attempts: + - Maximum 1 fix attempt per commit - Tracked by commit SHA - New commits allow new fix attempts ## Auto-undraft feature -When enabled (default), AutoDev automatically converts draft PRs to ready-for-review when all CI checks pass. +When enabled (default), DevBird automatically converts draft PRs to ready-for-review when all CI checks pass. -For details about this feature including when to enable/disable it and configuration options, see [Auto-undraft PR](/autodev/settings#auto-undraft-pr) in the settings documentation. +For details about this feature including when to enable/disable it and configuration options, see [Auto-undraft PR](/devbird/settings#auto-undraft-pr) in the settings documentation. ## GitHub Ruleset recommendations -To optimize AutoDev's automated workflow, we recommend configuring GitHub Rulesets to protect your repository while allowing AutoDev to work efficiently. +To optimize DevBird's automated workflow, we recommend configuring GitHub Rulesets to protect your repository while allowing DevBird to work efficiently. ### Recommended ruleset configuration **Branch protection rules:** + - **Require pull request reviews** - Ensure human oversight of AI-generated code - **Require status checks to pass** - Enforce CI validation before merging -- **Allow force pushes: Enable for AutoDev bot** - Let AutoDev clean up commit history after addressing reviews +- **Allow force pushes: Enable for DevBird bot** - Let DevBird clean up commit history after addressing reviews - **Allow deletions: Disable** - Protect branches from accidental deletion -**Why allow force pushes for AutoDev:** -When AutoDev addresses review feedback or fixes CI failures, it may need to force push to maintain a clean commit history. This is safe because: -- Only the AutoDev bot account has this permission +**Why allow force pushes for DevBird:** +When DevBird addresses review feedback or fixes CI failures, it may need to force push to maintain a clean commit history. This is safe because: + +- Only the DevBird bot account has this permission - Changes still go through PR review - CI checks must still pass - Human approval required for merge **Setting up the ruleset:** + 1. Go to your repository settings 2. Navigate to Rules → Rulesets 3. Create a new ruleset for your target branches (e.g., `main`, `develop`) 4. Configure branch protections as above -5. Under "Bypass list," add the AutoDev bot account for force push permissions +5. Under "Bypass list," add the DevBird bot account for force push permissions -This configuration ensures code quality while allowing AutoDev to manage PRs efficiently without manual intervention. +This configuration ensures code quality while allowing DevBird to manage PRs efficiently without manual intervention. ## Best practices ### For Reviewers **Be specific in feedback:** + ``` Please add error handling for the null case on line 45 ``` + Better than: + ``` Needs error handling ``` **Reference specific code:** + ``` In UserService.authenticateUser(), add rate limiting to prevent brute force attacks ``` **Provide context:** + ``` This approach won't work with our existing session management. Please use the SessionManager class instead. @@ -225,16 +267,19 @@ management. Please use the SessionManager class instead. ### For PR Authors **Monitor automated updates:** -- Check that AutoDev addressed your feedback + +- Check that DevBird addressed your feedback - Review changes made by AI - Add manual updates if needed **Collaborate with AI:** -- Request updates through AutoDev + +- Request updates through DevBird - Let AI handle repetitive fixes - Make final manual adjustments **Keep PRs focused:** + - Single responsibility per PR - Easier for AI to maintain - Faster review cycles @@ -243,13 +288,14 @@ management. Please use the SessionManager class instead. You can also manually request PR updates: -1. Go to AutoDev task details +1. Go to DevBird task details 2. Find the PR you want to update 3. Click **Update PR** 4. Enter update instructions -5. AutoDev converts PR to draft and makes changes +5. DevBird converts PR to draft and makes changes Use manual updates when: + - Review feedback is complex - Need additional features - Want to refine the implementation @@ -259,21 +305,22 @@ Use manual updates when: You can apply review feedback from other pull requests using the Reflect command: 1. Find the review comment you want to apply. -2. Copy the comment's direct link (e.g., `https://github.com/delinoio/autodev-example/pull/123#issuecomment-337041341`) +2. Copy the comment's direct link (e.g., `https://github.com/delinoio/devbird-example/pull/123#issuecomment-337041341`) 3. On the current PR, submit a review with "Request changes" -4. In the review message, use: `Reflect https://github.com/delinoio/autodev-example/pull/123#issuecomment-337041341` -5. AutoDev will analyze the linked review comment and apply those changes to the current PR +4. In the review message, use: `Reflect https://github.com/delinoio/devbird-example/pull/123#issuecomment-337041341` +5. DevBird will analyze the linked review comment and apply those changes to the current PR This is useful when: + - Applying reviews from other people ## Troubleshooting -For common PR review issues and solutions, see the [PR Review Troubleshooting](/autodev/troubleshooting/pr-reviews) guide. +For common PR review issues and solutions, see the [PR Review Troubleshooting](/devbird/troubleshooting/pr-reviews) guide. ## Next steps -- [PR Review Troubleshooting](/autodev/troubleshooting/pr-reviews) -- Configure [AutoDev Settings](/autodev/settings) -- Learn about [AI Reviewers](/autodev/reviewing-prs/ai-reviewer) -- Troubleshoot [Unit Tasks](/autodev/troubleshooting/unit-task) +- [PR Review Troubleshooting](/devbird/troubleshooting/pr-reviews) +- Configure [DevBird Settings](/devbird/settings) +- Learn about [AI Reviewers](/devbird/reviewing-prs/ai-reviewer) +- Troubleshoot [Unit Tasks](/devbird/troubleshooting/unit-task) diff --git a/autodev/settings/index.mdx b/devbird/settings/index.mdx similarity index 90% rename from autodev/settings/index.mdx rename to devbird/settings/index.mdx index cb467bc..1158ce6 100644 --- a/autodev/settings/index.mdx +++ b/devbird/settings/index.mdx @@ -1,9 +1,9 @@ --- title: Settings -description: Configure AutoDev behavior for your tenant +description: Configure DevBird behavior for your tenant --- -AutoDev provides several settings to control how it handles tasks, PRs, and reviews. Settings are configured at the tenant level (your team or user account) and apply to all repositories under that tenant. +DevBird provides several settings to control how it handles tasks, PRs, and reviews. Settings are configured at the tenant level (your team or user account) and apply to all repositories under that tenant. ## Accessing Settings @@ -18,26 +18,30 @@ AutoDev provides several settings to control how it handles tasks, PRs, and revi **Default**: Disabled -Controls whether AutoDev automatically triggers workflows when bot accounts submit PR reviews. +Controls whether DevBird automatically triggers workflows when bot accounts submit PR reviews. **When enabled:** + - Workflows trigger automatically on bot reviews - Uses GitHub App installation tokens - Bots don't need to connect the repository - All attempts are logged for debugging **Use cases:** + - AI code review tools (Claude Code, Cursor, GitHub Copilot) - AI-powered PR analysis and suggestions - Automated code quality assistants - AI pair programming tools **When to enable:** + - You have trusted bot integrations - You want fully automated workflows - You're using automated code review tools **When to disable:** + - You want manual control over bot-triggered workflows - You're concerned about excessive workflow runs - You prefer reviewing bot suggestions first @@ -46,27 +50,31 @@ Controls whether AutoDev automatically triggers workflows when bot accounts subm **Default**: Enabled -Controls whether AutoDev posts the full task prompt as a PR comment. +Controls whether DevBird posts the full task prompt as a PR comment. **When enabled:** + - Posts complete task prompt to PR comments - Provides full context to reviewers - Creates comprehensive audit trail - Makes task requirements transparent **When disabled:** + - Only posts task link comment - Cleaner PR comment section - Reduces comment noise - Reviewers access details via link **Best for enabling:** + - Teams who want inline context - Compliance/audit requirements - Transparent task tracking - Quick reference without clicking links **Best for disabling:** + - Teams preferring minimal PR comments - Projects with many automated tasks - When task details are sensitive @@ -78,27 +86,31 @@ Controls whether AutoDev posts the full task prompt as a PR comment. This feature is currently disabled globally due to a bug and is under development. The toggle appears disabled in the UI with a warning message. -Controls whether AutoDev automatically converts draft PRs to ready-for-review when CI passes. +Controls whether DevBird automatically converts draft PRs to ready-for-review when CI passes. **When enabled (after re-enablement):** + - Automatically marks PR ready when checks pass - Signals completion to team - Reduces manual workflow steps - Enables automated review requests **When disabled:** + - PRs remain in draft after CI passes - Manual conversion required - Additional quality control gate - Gives time for self-review **Best for enabling:** + - Fast-moving teams - High confidence in CI/CD - Automated workflows - Trust in AI agent output **Best for disabling:** + - Teams wanting manual review gates - Additional quality assurance needed - Learning/training environments @@ -110,9 +122,10 @@ Controls whether AutoDev automatically converts draft PRs to ready-for-review wh **Purpose**: Configure default AI agent and model for CompositeTask planning phase -These settings control which AI agent and model are used when AutoDev generates task graphs for composite tasks. +These settings control which AI agent and model are used when DevBird generates task graphs for composite tasks. **Planning Agent Options:** + - `claude_code` - Claude Code agent (recommended) - `opencode` - OpenCode agent - `crush_cli` - Crush CLI agent @@ -121,17 +134,21 @@ These settings control which AI agent and model are used when AutoDev generates - `github_copilot_cli` - GitHub Copilot CLI agent **Planning Model Options:** + - Varies by agent (e.g., `sonnet`, `opus`, `haiku` for Claude Code) **When set:** + - New composite tasks use these defaults for AI planning - Generates task breakdown and dependency graph - Creates execution plan **When not set:** + - System defaults are used **Use cases:** + - Choose more powerful models for complex project planning - Select faster/cheaper models for simple decomposition - Match agent capabilities to your planning needs @@ -141,6 +158,7 @@ These settings control which AI agent and model are used when AutoDev generates **Purpose**: Configure default AI agent and model for task execution These settings control which AI agent and model are used when: + - Creating and executing unit tasks - Executing individual nodes in composite task graphs @@ -151,14 +169,17 @@ Same as planning agent options above. Varies by agent. **When set:** + - Unit tasks use these defaults - Composite task nodes use these defaults - Actual code writing and PR creation uses these **When not set:** + - System defaults are used **Use cases:** + - Different agent for planning vs. execution (e.g., powerful planner, fast executor) - Balance cost and quality across workflow phases - Optimize for execution speed or quality @@ -170,17 +191,20 @@ Varies by agent. Controls whether newly created composite tasks have auto-approval enabled by default. **When enabled:** + - New composite tasks are created with auto-approval turned on -- After planning completes, ecution starts automatically +- After planning completes, ecution starts automatically - Ready nodes are automatically approved without manual review - Full workflow automation from creation to completion **When disabled:** + - New composite tasks require manual execution start - Each ready node requires manual approval - More control over task progression **What happens with auto-approval:** + 1. You create a composite task 2. AI planning completes automatically 3. **Execution starts automatically** (no "Start Execution" click needed) @@ -190,16 +214,18 @@ Controls whether newly created composite tasks have auto-approval enabled by def **Note**: This setting only affects NEW composite tasks at creation time. You can still manually toggle auto-approval on individual composite tasks after they're created. **Best for enabling:** + - Trusted workflows - Repetitive tasks - High confidence in AI planning - Want hands-off automation **Best for disabling:** + - Want to review plans before execution - Need to modify prompts before running - Careful control over task progression -- Learning/evaluating AutoDev +- Learning/evaluating DevBird ## Configuration Tips @@ -238,6 +264,7 @@ Provides maximum control and review opportunities at each step. ### Settings not saving **Check:** + 1. Verify you have tenant admin permissions 2. Refresh the page and try again 3. Check browser console for errors @@ -246,6 +273,7 @@ Provides maximum control and review opportunities at each step. ### Settings not taking effect **Verify:** + 1. Settings page shows your changes 2. Wait a few minutes for propagation 3. Test with a new task/PR (not existing ones) @@ -254,18 +282,20 @@ Provides maximum control and review opportunities at each step. ### Bot reviews not triggering workflows **When "Auto-apply Bot Reviews" is enabled:** + 1. Verify bot account exists in your organization 2. Check GitHub webhook deliveries for errors 3. Ensure bot has correct permissions 4. Review workflow logs for failures **When disabled:** + - This is expected behavior - Enable the setting if you want automation ## Next Steps -- [Create your first task](/autodev/tasks) -- [Configure AI agents](/autodev/ai-agents/claude-code) -- [Review PRs efficiently](/autodev/reviewing-prs) -- [Troubleshoot common issues](/autodev/troubleshooting/unit-task) +- [Create your first task](/devbird/tasks) +- [Configure AI agents](/devbird/ai-agents/claude-code) +- [Review PRs efficiently](/devbird/reviewing-prs) +- [Troubleshoot common issues](/devbird/troubleshooting/unit-task) diff --git a/autodev/tasks/composite/index.mdx b/devbird/tasks/composite/index.mdx similarity index 94% rename from autodev/tasks/composite/index.mdx rename to devbird/tasks/composite/index.mdx index 32d6290..26a97d1 100644 --- a/autodev/tasks/composite/index.mdx +++ b/devbird/tasks/composite/index.mdx @@ -3,13 +3,15 @@ title: "Composite Tasks" description: "Break down complex projects into AI-planned coordinated tasks" --- -Composite tasks use AI to break down complex projects into multiple coordinated steps. AutoDev creates a task graph showing dependencies and execution order, allowing parallel work while ensuring tasks build on each other correctly. +Composite tasks use AI to break down complex projects into multiple coordinated steps. DevBird creates a task graph showing dependencies and execution order, allowing parallel work while ensuring tasks build on each other correctly. ## How composite tasks work ### 1. AI Planning Phase + When you create a composite task: -- AutoDev analyzes your request + +- DevBird analyzes your request - AI generates a task graph (DAG structure) - Tasks are organized with dependencies - Plan is saved for your review @@ -17,7 +19,9 @@ When you create a composite task: Status: **Planning** ### 2. Review and Start + After planning completes: + - View the task graph visualization - See all tasks and their dependencies - Review the execution plan @@ -27,6 +31,7 @@ After planning completes: Status: **Pending** → **In Progress** **Auto-Start Behavior**: + - When `auto_approval_enabled` is true, execution starts automatically after planning - No "Start Execution" button click needed - Initial nodes (without dependencies) are marked as "ready" immediately @@ -34,7 +39,9 @@ Status: **Pending** → **In Progress** - Can be configured via tenant settings or per-task toggle ### 3. Task Execution + Tasks execute based on dependencies: + - Initial tasks (no dependencies) become **Ready** - You approve each ready task - Approved tasks spawn unit tasks @@ -42,13 +49,15 @@ Tasks execute based on dependencies: - New tasks become ready as dependencies complete ### 4. Completion + When all tasks finish: + - Composite task status: **Completed** - All pull requests are created ## Creating a composite task -1. Go to your AutoDev dashboard +1. Go to your DevBird dashboard 2. Select your repository 3. Enter your complex project description 4. **Check "Create as Composite Task"** @@ -63,7 +72,9 @@ When all tasks finish: The task graph shows: ### Nodes + Each node represents a task to be completed: + - **Pending** (gray) - Waiting for dependencies - **Ready** (blue) - Dependencies met, awaiting approval - **Approved** (yellow) - Approved, about to start @@ -73,12 +84,16 @@ Each node represents a task to be completed: - **Blocked** (dark gray) - Cannot proceed due to failed dependency ### Edges + Arrows show dependencies: + - Task A → Task B means B depends on A - Task B starts only after Task A completes ### Parallel execution + Tasks without dependencies on each other run in parallel: + ``` Task A / \ @@ -108,6 +123,7 @@ Enable auto-approval to run tasks automatically: **Two-Level Auto-Approval:** 1. **Tenant-Level Default** (Settings): + - Set "Default Composite Task Auto-Approval" in tenant settings - Determines auto-approval status for NEW composite tasks - Existing tasks are not affected @@ -120,6 +136,7 @@ Enable auto-approval to run tasks automatically: **What Auto-Approval Enables:** 1. **Auto-Start Execution** (after planning completes): + - No need to click "Start Execution" - Automatically transitions from "pending" to "in_progress" - Initial nodes become "ready" immediately @@ -130,6 +147,7 @@ Enable auto-approval to run tasks automatically: - Continuous task progression Use auto-approval when: + - You trust the AI-generated plan - Tasks are well-defined and low-risk - You want continuous progress without manual steps @@ -137,6 +155,7 @@ Use auto-approval when: - Full automation from creation to completion Disable auto-approval when: + - You want to review each task before execution - Tasks require careful sequencing - You want to modify prompts before execution @@ -150,6 +169,7 @@ Disable auto-approval when: View comprehensive information: **Overview section:** + - Title and description - Repository and branch - Progress (X/Y tasks completed) @@ -157,27 +177,32 @@ View comprehensive information: - Creation time **Task graph visualization:** + - Interactive diagram of all tasks - Color-coded status indicators - Click nodes to see details - View dependencies **Ready for approval:** + - List of tasks ready to execute - Option to modify prompts - Approve or reject buttons **Active tasks:** + - Currently executing tasks - Links to spawned unit tasks - Real-time status **Completed tasks:** + - Finished tasks - Links to pull requests - Merge status **Failed/blocked tasks:** + - Failed tasks with error details - Retry options - Blocked tasks showing required dependencies @@ -187,6 +212,7 @@ View comprehensive information: You can edit task prompts before execution: **During approval:** + 1. Task becomes ready 2. Review the AI-generated prompt 3. Click **Edit Prompt** @@ -194,6 +220,7 @@ You can edit task prompts before execution: 5. Approve to execute with modified prompt **Before approval:** + 1. Go to task graph visualization 2. Click on a task node (must be pending, ready, or blocked) 3. Edit the prompt and title @@ -217,7 +244,7 @@ The sync feature checks all tasks and updates statuses: 1. Go to composite task details 2. Click **Sync Composite Task** -3. AutoDev checks all tasks and PRs: +3. DevBird checks all tasks and PRs: - Updates PR merge statuses from GitHub - Marks completed tasks when PRs are merged - Recalculates node readiness @@ -225,6 +252,7 @@ The sync feature checks all tasks and updates statuses: - Updates composite task progress Returns: + - Tasks updated count - Nodes updated count - PRs synced count @@ -234,15 +262,17 @@ Returns: ### How AI creates the plan -AutoDev uses advanced prompting to create efficient task graphs: +DevBird uses advanced prompting to create efficient task graphs: **Planning priorities:** + 1. **Minimize rebasing** - Structure for parallel execution 2. **CI/Infrastructure first** - Set up testing before features 3. **Independent code paths** - Tasks touch different files 4. **Clear boundaries** - Define interfaces early **Task ordering:** + - Phase 1: CI/Infrastructure (no dependencies) - Phase 2: Database/Storage setup - Phase 3: Core contracts (APIs, models) @@ -251,12 +281,14 @@ AutoDev uses advanced prompting to create efficient task graphs: - Phase 6: Polish (UI, performance, docs) **Graph structure:** + - Wide and shallow (more parallel, fewer sequential) - Each task represents meaningful progress ### Writing effective composite task prompts **Include comprehensive context:** + ``` Build a complete e-commerce checkout system including: - Shopping cart with session persistence @@ -267,6 +299,7 @@ Build a complete e-commerce checkout system including: ``` **Specify technical requirements:** + ``` Migrate to microservices architecture using: - Docker containers for each service @@ -277,6 +310,7 @@ Migrate to microservices architecture using: ``` **Reference documentation:** + ``` Implement authentication following our architecture: - Reference: @docs/auth-architecture.md @@ -298,6 +332,7 @@ Deleting a composite task: ## Example composite task **Prompt:** + ``` Build a user authentication system with email verification and OAuth ``` @@ -332,21 +367,25 @@ Tasks 3, 4, and 5 run in parallel after task 2 completes. ## Benefits of composite tasks ### Coordinated execution + - Tasks build on each other - Dependencies ensure correct order - Parallel work speeds completion ### AI-powered planning + - Optimal task breakdown - Smart dependency management - Efficient parallelization ### Flexibility + - Modify prompts before execution - Retry failed tasks - Enable/disable auto-approval ### Visibility + - See entire project plan upfront - Track progress across all tasks - Understand dependencies @@ -356,32 +395,37 @@ Tasks 3, 4, and 5 run in parallel after task 2 completes. Composite tasks excel at applying the same logic across multiple independent items, creating separate PRs for each one. This is ideal for: **Translation and localization:** + ``` -Review all AutoDev documentation pages one by one and fix awkward translations. +Review all DevBird documentation pages one by one and fix awkward translations. Check each supported language individually. Create one PR per page. Only create PRs if translations need fixing. ``` -AutoDev will: +DevBird will: + - Plan separate tasks for each documentation page - Apply the same review logic to each language version - Create individual PRs only when improvements are needed - Process pages in parallel for faster completion **Pro tip**: Creating one task per page is highly effective because: + - **Parallelization**: Multiple pages are processed simultaneously - **Focus**: Each AI agent works on a single page, preventing the common issue of AI agents forgetting their tasks midway through complex work - **Isolation**: Problems in one page don't affect others Example prompt: + ``` -Make the translation of each AutoDev page smooth and natural. +Make the translation of each DevBird page smooth and natural. Create one task per page. Each task should handle one page. Each task should not create a PR if there are no translation issues. ``` **Codebase-wide refactoring:** + ``` Update all API endpoints to use the new authentication middleware. Create one PR per endpoint group. @@ -391,6 +435,7 @@ Ensure backward compatibility in each change. ## When not to use composite tasks Use unit tasks instead when: + - Task is straightforward and single-purpose - No dependencies on other work - Quick fix or small change @@ -398,10 +443,10 @@ Use unit tasks instead when: ## Troubleshooting -See the [Composite Task Troubleshooting](/autodev/troubleshooting/composite-task) guide for common issues. +See the [Composite Task Troubleshooting](/devbird/troubleshooting/composite-task) guide for common issues. ## Next steps -- Learn about [Unit Tasks](/autodev/tasks/unit) -- Understand [PR Review Process](/autodev/reviewing-prs) -- Configure [AI Agents](/autodev/ai-agents/claude-code) +- Learn about [Unit Tasks](/devbird/tasks/unit) +- Understand [PR Review Process](/devbird/reviewing-prs) +- Configure [AI Agents](/devbird/ai-agents/claude-code) diff --git a/autodev/tasks/index.mdx b/devbird/tasks/index.mdx similarity index 82% rename from autodev/tasks/index.mdx rename to devbird/tasks/index.mdx index 0d837c9..63fe617 100644 --- a/autodev/tasks/index.mdx +++ b/devbird/tasks/index.mdx @@ -1,13 +1,13 @@ --- title: "Understanding Tasks" -description: "Learn about the two types of tasks in AutoDev and when to use each" +description: "Learn about the two types of tasks in DevBird and when to use each" --- -AutoDev offers two types of tasks to handle different development scenarios: **Unit Tasks** for straightforward work and **Composite Tasks** for complex projects. +DevBird offers two types of tasks to handle different development scenarios: **Unit Tasks** for straightforward work and **Composite Tasks** for complex projects. ## Unit Tasks -Unit tasks are perfect for single, well-defined development tasks. When you create a unit task, AutoDev's AI agent: +Unit tasks are perfect for single, well-defined development tasks. When you create a unit task, DevBird's AI agent: 1. Analyzes your request 2. Writes the necessary code @@ -39,11 +39,11 @@ Refactor the payment processing service to use the new API ## Composite Tasks -Composite tasks are designed for complex projects that require multiple coordinated steps. AutoDev uses AI to break down your request into a task graph (DAG structure) where tasks can run in parallel or sequence based on dependencies. +Composite tasks are designed for complex projects that require multiple coordinated steps. DevBird uses AI to break down your request into a task graph (DAG structure) where tasks can run in parallel or sequence based on dependencies. ### How composite tasks work -1. **AI Planning** - AutoDev analyzes your request and creates a task graph +1. **AI Planning** - DevBird analyzes your request and creates a task graph 2. **Review Plan** - You see the proposed tasks and their dependencies 3. **Start Execution** - You approve the plan and start execution 4. **Sequential Execution** - Tasks become ready as dependencies complete @@ -80,17 +80,21 @@ and monitoring Both task types support optional configuration: ### Repository selection -Choose which repository the AI should work on. You can only select repositories where you've installed the AutoDev GitHub App. + +Choose which repository the AI should work on. You can only select repositories where you've installed the DevBird GitHub App. ### AI Agent selection (Optional) -Choose which AI coding agent to use. See [available AI agents](/autodev/getting-started/ai-agent) for the full list. -If not specified, AutoDev uses your team's default agent. +Choose which AI coding agent to use. See [available AI agents](/devbird/getting-started/ai-agent) for the full list. + +If not specified, DevBird uses your team's default agent. ### Model version (Optional) + Specify the AI model version (e.g., "sonnet", "gpt-4"). If not specified, the agent's default model is used. ### Base branch (Optional) + Specify which branch to use as the base for the task. Defaults to your repository's default branch (usually `main` or `master`). ## Task Status @@ -105,7 +109,7 @@ Tasks progress through different statuses: ## Pull Requests -Each task can create multiple pull requests. AutoDev automatically: +Each task can create multiple pull requests. DevBird automatically: - Creates descriptive PR titles and descriptions - Links PRs back to the task @@ -116,6 +120,6 @@ Each task can create multiple pull requests. AutoDev automatically: ## Next steps -- Learn about [Unit Tasks](/autodev/tasks/unit) -- Learn about [Composite Tasks](/autodev/tasks/composite) -- See [Creating your first PR](/autodev/getting-started/first-pr) +- Learn about [Unit Tasks](/devbird/tasks/unit) +- Learn about [Composite Tasks](/devbird/tasks/composite) +- See [Creating your first PR](/devbird/getting-started/first-pr) diff --git a/autodev/tasks/unit/index.mdx b/devbird/tasks/unit/index.mdx similarity index 84% rename from autodev/tasks/unit/index.mdx rename to devbird/tasks/unit/index.mdx index db8f60f..c85b5c1 100644 --- a/autodev/tasks/unit/index.mdx +++ b/devbird/tasks/unit/index.mdx @@ -3,11 +3,11 @@ title: "Unit Tasks" description: "Create and manage single-focus development tasks with AI automation" --- -Unit tasks are AutoDev's building blocks for straightforward development work. Each unit task focuses on a single objective and can generate multiple pull requests to complete it. +Unit tasks are DevBird's building blocks for straightforward development work. Each unit task focuses on a single objective and can generate multiple pull requests to complete it. ## Creating a unit task -1. Navigate to your AutoDev dashboard +1. Navigate to your DevBird dashboard 2. Select your repository from the dropdown 3. Enter your task description in the prompt field 4. **Leave "Create as Composite Task" unchecked** for unit tasks @@ -20,16 +20,20 @@ Unit tasks are AutoDev's building blocks for straightforward development work. E ## Task lifecycle ### 1. Pending -Your task is created and queued for execution. AutoDev prepares to trigger the GitHub Actions workflow. + +Your task is created and queued for execution. DevBird prepares to trigger the GitHub Actions workflow. ### 2. In Progress + The AI agent is actively working on your task: + - Analyzing your requirements - Writing code - Creating pull requests - Running tests -**Detailed Status**: When a task is in progress, AutoDev shows detailed information about what's currently happening: +**Detailed Status**: When a task is in progress, DevBird shows detailed information about what's currently happening: + - "Creating initial implementation..." - AI is writing the first version - "Addressing PR review feedback..." - Responding to review comments - "Fixing CI failures..." - Attempting to fix failing tests @@ -38,13 +42,17 @@ The AI agent is actively working on your task: This gives you real-time visibility into the current workflow execution phase. ### 3. Completed + The task is marked complete when all pull requests are merged. This means: + - All code changes have been reviewed and approved - All PRs have been merged to their target branches - The task objectives have been successfully implemented ### 4. Failed + The task encountered an error. Common reasons: + - GitHub Actions workflow failed - Invalid configuration - AI agent encountered an issue @@ -56,6 +64,7 @@ You can retry failed tasks from the task details page. The task details page shows: ### Task overview + - Task title (automatically generated from your prompt) - Original prompt - Repository and branch information @@ -63,7 +72,9 @@ The task details page shows: - Creation timestamp ### Pull requests + All PRs created for this task: + - PR title and number - Status (open/closed/merged) - CI check results @@ -71,18 +82,22 @@ All PRs created for this task: - Links to GitHub ### Workflow executions + History of all workflow runs for this task, including: **Direct task workflows:** + - Task creation - Initial implementation - Task retries - Retry after failure **PR-related workflows:** + - PR updates - Manual update requests - PR reviews - Responses to review feedback - PR CI fixes - Automatic fixes for failing checks **Details shown:** + - Execution status (pending/in_progress/completed/failed) - Workflow type - Timestamps (created, started, completed) @@ -92,25 +107,28 @@ History of all workflow runs for this task, including: ## Managing pull requests ### Automatic PR comments -When a PR is created, AutoDev adds two types of comments: + +When a PR is created, DevBird adds two types of comments: **Task link comment** (always added): -- Links back to the AutoDev task + +- Links back to the DevBird task - Provides context for reviewers **Task prompt comment** (optional, enabled by default): + - Shows the original task prompt - Helps reviewers understand the AI's instructions -- Can be disabled in [Settings](/autodev/settings) +- Can be disabled in [Settings](/devbird/settings) ### PR workflow 1. **PR Creation** - AI creates PR and opens it for review 2. **Draft Status** - PR is converted to draft during automated updates 3. **Code Review** - Team members review the changes -4. **AI Responds** - AutoDev automatically responds to review comments +4. **AI Responds** - DevBird automatically responds to review comments 5. **CI Checks** - Automated tests run -6. **CI Fixes** - AutoDev fixes failing checks automatically +6. **CI Fixes** - DevBird fixes failing checks automatically 7. **Ready to Merge** - PR is undrafted when all checks pass ## Updating a pull request @@ -121,7 +139,7 @@ You can manually request updates to any PR: 2. Find the PR you want to update 3. Click **Update PR** 4. Enter your update instructions -5. AutoDev converts the PR to draft and makes the changes +5. DevBird converts the PR to draft and makes the changes ## Retrying a task @@ -137,7 +155,7 @@ Use the sync feature to refresh task status from GitHub: 1. Go to the task details page 2. Click **Sync Task** in the Debug menu -3. AutoDev checks all PRs and updates the task status automatically: +3. DevBird checks all PRs and updates the task status automatically: - **All PRs merged** → Task marked as completed - **All PRs closed without merge** → Task marked as failed - **PRs still open** → Status remains in progress @@ -145,6 +163,7 @@ Use the sync feature to refresh task status from GitHub: ## Deleting a task Deleting a task: + - Closes all open pull requests - Cancels any running workflows - Removes the task from your dashboard @@ -154,58 +173,72 @@ Deleting a task: ## Best practices ### Write clear prompts + Be specific about what you want: **Good prompts:** + ``` Fix the null pointer exception in UserService.java when email is missing ``` + ``` Add rate limiting to the /api/auth endpoint with 10 requests per minute ``` + ``` Update the user profile page to show avatar upload with preview ``` **Avoid vague prompts:** + ``` Fix the bug ``` + ``` Make it better ``` + ``` Update the code ``` ### Include context + Reference specific files, functions, or error messages: + ``` Fix the CORS error on line 45 of server.js when calling from localhost:3000 ``` ### Use file references + Include file paths with `@` for better AI understanding: + ``` Refactor @src/services/payment.ts to use the new PaymentProcessor interface ``` ### Specify requirements + Include technical requirements or constraints: + ``` Add user authentication using JWT tokens with 24-hour expiration, stored in httpOnly cookies ``` ### Break down large tasks -For complex work, consider using [Composite Tasks](/autodev/tasks/composite) or creating multiple unit tasks. + +For complex work, consider using [Composite Tasks](/devbird/tasks/composite) or creating multiple unit tasks. ## Troubleshooting -See the [Unit Task Troubleshooting](/autodev/troubleshooting/unit-task) guide for common issues and solutions. +See the [Unit Task Troubleshooting](/devbird/troubleshooting/unit-task) guide for common issues and solutions. ## Next steps -- Learn about [Composite Tasks](/autodev/tasks/composite) -- Understand [PR Review Process](/autodev/reviewing-prs) -- Configure [AI Agents](/autodev/ai-agents/claude-code) +- Learn about [Composite Tasks](/devbird/tasks/composite) +- Understand [PR Review Process](/devbird/reviewing-prs) +- Configure [AI Agents](/devbird/ai-agents/claude-code) diff --git a/autodev/troubleshooting/ai-reviewer.mdx b/devbird/troubleshooting/ai-reviewer.mdx similarity index 91% rename from autodev/troubleshooting/ai-reviewer.mdx rename to devbird/troubleshooting/ai-reviewer.mdx index f5063c2..1cf2979 100644 --- a/autodev/troubleshooting/ai-reviewer.mdx +++ b/devbird/troubleshooting/ai-reviewer.mdx @@ -1,32 +1,36 @@ --- title: "AI Reviewer Troubleshooting" -description: "Troubleshoot bot reviews and auto-apply issues in AutoDev" +description: "Troubleshoot bot reviews and auto-apply issues in DevBird" --- -This document is still under review. The content may be inaccurate or outdated. + This document is still under review. The content may be inaccurate or + outdated. ## Bot Reviews Not Triggering Workflows **Symptoms:** + - Bot submits review - No workflow triggered - PR not updated **Common Cause:** -Auto-apply bot reviews may be disabled. See [troubleshooting bot reviews](/autodev/settings#bot-reviews-not-triggering-workflows) in the settings documentation for complete troubleshooting steps. +Auto-apply bot reviews may be disabled. See [troubleshooting bot reviews](/devbird/settings#bot-reviews-not-triggering-workflows) in the settings documentation for complete troubleshooting steps. **Quick Solutions:** **Check bot account type:** + 1. Go to bot's GitHub profile 2. Verify it shows "Bot" badge 3. Check via API: `https://api.github.com/users/{bot-username}` 4. Look for `"type": "Bot"` in response **Manual trigger alternative:** + - Use "Update PR" feature - Manually apply bot feedback - Trigger workflow explicitly @@ -34,12 +38,14 @@ Auto-apply bot reviews may be disabled. See [troubleshooting bot reviews](/autod ## Too Many Bot Workflows **Symptoms:** + - Bots triggering too many workflows - High costs - Excessive automation - Workflow queue backlog **Causes:** + - Multiple bots reviewing same PR - Bots reviewing too frequently - Auto-apply enabled with many bots @@ -48,23 +54,27 @@ Auto-apply bot reviews may be disabled. See [troubleshooting bot reviews](/autod **Solutions:** **Disable auto-apply:** + - Temporarily turn off the feature - Manually review bot feedback - Selectively apply changes **Configure bots to review less:** + - Adjust bot settings in repository - Reduce review frequency - Filter what bots review - Limit bot triggers **Monitor usage:** + - Check costs - Review workflow execution history - Identify which bots trigger most workflows - Adjust bot configuration accordingly **Cost optimization:** + ``` Each bot review = 1 workflow execution 1 execution = $0.03 @@ -74,12 +84,14 @@ Multiple bots × frequent reviews = high costs ## Bot Feedback Not Applied Correctly **Symptoms:** + - Workflow runs but doesn't fix issues - Bot re-reviews with same feedback - Changes don't match bot requests - AI misunderstands bot comments **Causes:** + - Bot feedback unclear for AI - Complex fixes beyond AI capability - Conflicting feedback from multiple bots @@ -88,24 +100,28 @@ Multiple bots × frequent reviews = high costs **Solutions:** **Review workflow logs:** + 1. Check what AI agent attempted 2. See if it understood bot feedback 3. Identify where it failed 4. Look for error messages **Manual intervention:** + 1. Disable auto-apply temporarily 2. Manually fix based on bot feedback 3. Push updates to PR 4. Re-enable auto-apply after resolution **Improve bot feedback:** + - Configure bots to give specific guidance - Use structured feedback formats - Limit scope of bot reviews - Ensure bots provide file paths and line numbers **Example of good bot feedback:** + ``` In src/utils/auth.js:45, change: if (user == null) @@ -116,6 +132,7 @@ Use strict equality for null checks. ``` **Example of poor bot feedback:** + ``` Fix the equality checks ``` @@ -123,12 +140,14 @@ Fix the equality checks ## Bots Not Detected **Symptoms:** + - Bot has "Bot" badge on GitHub - Auto-apply enabled - Reviews still don't trigger workflows - Bot appears to be ignored **Causes:** + - Bot account not properly configured - GitHub API inconsistency - Webhook not receiving bot reviews @@ -137,24 +156,28 @@ Fix the equality checks **Solutions:** **Verify bot configuration:** + 1. Check bot is properly installed on repository 2. Verify bot has review permissions 3. Confirm bot is active **Test with manual trigger:** + 1. Have bot submit review 2. Manually use "Update PR" feature 3. Paste bot feedback 4. See if AI can handle it **Check webhook logs:** + 1. Repository settings → Webhooks -2. Find AutoDev webhook +2. Find DevBird webhook 3. Check for bot review events 4. Verify event payload contains bot info **Alternative solution:** -- Contact AutoDev support + +- Contact DevBird support - Provide bot account details - Share webhook logs - Request investigation @@ -162,12 +185,14 @@ Fix the equality checks ## Conflicting Bot Reviews **Symptoms:** + - Multiple bots review same PR - Give conflicting feedback - AI applies one fix, breaks another - Endless update loop **Causes:** + - Bots have different standards - One bot's fix triggers another bot's review - Circular dependencies in bot rules @@ -176,18 +201,21 @@ Fix the equality checks **Solutions:** **Disable auto-apply for conflicting bots:** + 1. Turn off auto-apply temporarily 2. Manually reconcile bot feedback 3. Apply fixes that satisfy all bots 4. Re-enable auto-apply **Configure bots to align:** + 1. Review bot configuration files 2. Ensure linting rules are compatible 3. Disable overlapping checks 4. Use single bot for similar checks **Manual reconciliation:** + 1. Collect all bot feedback 2. Identify conflicts 3. Determine correct approach @@ -195,6 +223,7 @@ Fix the equality checks 5. Test with all bots **Example:** + ``` ESLint: Use single quotes Prettier: Use double quotes @@ -205,12 +234,14 @@ Solution: Configure both to use same quote style ## Bot Review Permissions **Symptoms:** + - Bot cannot submit reviews - Bot comments appear but not as reviews - Auto-apply doesn't recognize bot feedback - Bot shows access errors **Causes:** + - Bot lacks review permissions - Bot not invited to repository - Bot installation incomplete @@ -219,18 +250,21 @@ Solution: Configure both to use same quote style **Solutions:** **Grant bot review permissions:** + 1. Repository settings → Collaborators 2. Add bot account if missing 3. Grant "Write" permission minimum 4. Ensure bot can access repository **For GitHub App bots:** + 1. Check app installation 2. Verify repository is included 3. Review app permissions 4. Reinstall app if needed **Check bot configuration:** + 1. Review bot's settings 2. Verify repository is enabled 3. Check bot is active @@ -239,12 +273,14 @@ Solution: Configure both to use same quote style ## Webhook Not Receiving Bot Events **Symptoms:** + - Manual reviews trigger workflows - Bot reviews don't - Webhook logs show user reviews but not bot reviews -- Bot reviews invisible to AutoDev +- Bot reviews invisible to DevBird **Causes:** + - Webhook event filters - GitHub webhook configuration - Bot reviews sent differently @@ -253,58 +289,67 @@ Solution: Configure both to use same quote style **Solutions:** **Check webhook event subscriptions:** + 1. Repository settings → Webhooks -2. Click AutoDev webhook +2. Click DevBird webhook 3. Verify "Pull request reviews" is checked 4. Save webhook configuration **Test webhook delivery:** + 1. Have bot submit review 2. Check webhook Recent Deliveries 3. Look for review event 4. Check event payload **Verify event format:** + 1. Review webhook payload 2. Ensure contains reviewer info 3. Check reviewer type field 4. Verify action is "submitted" **Re-register webhook:** -1. Remove AutoDev webhook -2. Reinstall AutoDev GitHub App + +1. Remove DevBird webhook +2. Reinstall DevBird GitHub App 3. Webhook will be recreated 4. Test with bot review ## Rate Limiting Issues **Symptoms:** + - First bot review works - Subsequent reviews don't trigger workflows - Error messages about rate limits - Workflows rejected **Causes:** + - GitHub API rate limiting -- AutoDev usage limits +- DevBird usage limits - Too many workflow triggers - Excessive bot activity **Solutions:** **GitHub API limits:** + - Wait for rate limit reset (usually 1 hour) - Reduce bot review frequency - Stagger bot reviews - Contact GitHub for higher limits -**AutoDev usage limits:** +**DevBird usage limits:** + - Check usage - Upgrade plan if needed - Optimize bot usage - Disable less important bots **Reduce bot activity:** + ``` Current: 10 bots × 5 reviews/day = 50 workflows Optimized: 3 bots × 2 reviews/day = 6 workflows @@ -312,10 +357,10 @@ Optimized: 3 bots × 2 reviews/day = 6 workflows ## Best Practices -For best practices on configuring bot reviews, monitoring costs, and regular auditing, see the [Auto-apply Bot Reviews configuration tips](/autodev/settings#configuration-tips) in the settings documentation. +For best practices on configuring bot reviews, monitoring costs, and regular auditing, see the [Auto-apply Bot Reviews configuration tips](/devbird/settings#configuration-tips) in the settings documentation. ## Next Steps -- [AI Reviewer Configuration](/autodev/reviewing-prs/ai-reviewer) -- [PR Review Process](/autodev/reviewing-prs) -- [Unit Task Troubleshooting](/autodev/troubleshooting/unit-task) +- [AI Reviewer Configuration](/devbird/reviewing-prs/ai-reviewer) +- [PR Review Process](/devbird/reviewing-prs) +- [Unit Task Troubleshooting](/devbird/troubleshooting/unit-task) diff --git a/autodev/troubleshooting/composite-task.mdx b/devbird/troubleshooting/composite-task.mdx similarity index 96% rename from autodev/troubleshooting/composite-task.mdx rename to devbird/troubleshooting/composite-task.mdx index 90a350c..f4112f6 100644 --- a/autodev/troubleshooting/composite-task.mdx +++ b/devbird/troubleshooting/composite-task.mdx @@ -4,21 +4,24 @@ description: "Common issues with composite tasks and task graphs" --- -This document is still under review. The content may be inaccurate or outdated. + This document is still under review. The content may be inaccurate or + outdated. -This guide helps you troubleshoot common issues with composite tasks and task graph execution in AutoDev. +This guide helps you troubleshoot common issues with composite tasks and task graph execution in DevBird. ## Planning Phase Issues ### Planning Stuck or Takes Too Long **Symptoms:** + - Composite task stuck in "Planning" status - Planning workflow running for 30+ minutes - No task graph generated **Possible Causes:** + 1. Complex project requiring extensive planning 2. Vague or unclear prompt 3. Workflow timeout @@ -27,16 +30,19 @@ This guide helps you troubleshoot common issues with composite tasks and task gr **Solutions:** **Check planning workflow status:** + 1. Go to GitHub Actions 2. Find the planning workflow run 3. Check logs for errors or stuck steps **Simplify the prompt:** + - Break very large projects into smaller composite tasks - Be more specific about requirements - Provide clear scope boundaries **Retry planning:** + 1. Delete the composite task 2. Create new task with refined prompt 3. Monitor planning progress @@ -44,6 +50,7 @@ This guide helps you troubleshoot common issues with composite tasks and task gr ### No Plan Generated **Symptoms:** + - Planning completes but no task graph appears - Status changes from "Planning" to "Failed" - Error: "Failed to generate plan" @@ -51,6 +58,7 @@ This guide helps you troubleshoot common issues with composite tasks and task gr **Solutions:** **Check planning workflow logs:** + ``` Look for: - "Generating task graph..." @@ -59,17 +67,20 @@ Look for: ``` **Verify prompt is actionable:** + - Does it describe a concrete project? - Are requirements clear? - Is scope reasonable for AI planning? **Example good prompts:** + ``` Build a REST API for user management with authentication, CRUD operations, and testing ``` **Example problematic prompts:** + ``` Make the app better Build something cool @@ -78,11 +89,13 @@ Build something cool ### Invalid Task Graph **Symptoms:** + - Plan uploaded but status shows "Failed" - Error: "Invalid task graph structure" - Circular dependencies detected **Causes:** + - AI generated invalid DAG structure - Circular dependencies in plan - Missing required fields @@ -90,10 +103,12 @@ Build something cool **Solutions:** **This is rare - usually indicates:** + - Very complex/unclear requirements - Edge case in planning algorithm **Retry with clearer prompt:** + 1. Delete failed composite task 2. Simplify project description 3. Break into smaller composite tasks @@ -104,12 +119,14 @@ Build something cool ### No Tasks Marked as Ready **Symptoms:** + - Clicked "Start Execution" - Status is "In Progress" - But no tasks show as "Ready" - Nothing happens **Causes:** + - All nodes have dependencies (no starting point) - Graph structure issue - Status calculation error @@ -117,12 +134,14 @@ Build something cool **Solutions:** **Use Sync feature:** + 1. Composite task details page 2. Click "Sync Composite Task" 3. System recalculates node statuses 4. Initial nodes should become ready **Check task graph visualization:** + - Are there nodes without dependencies? - These should be ready first - If all nodes have dependencies, graph is invalid @@ -130,6 +149,7 @@ Build something cool ### Tasks Not Becoming Ready **Symptoms:** + - Some tasks completed - But dependent tasks not marked as ready - Tasks stuck in "Pending" or "Blocked" @@ -137,18 +157,21 @@ Build something cool **Solutions:** **Sync composite task:** + 1. Go to composite task details 2. Click "Sync Composite Task" 3. System checks dependencies 4. Updates node readiness **What Sync does:** + - Checks all task PRs in GitHub - Updates merge statuses - Recalculates dependencies - Marks ready nodes **Check dependency completion:** + - All dependencies must be "Completed" - If any dependency "Failed", node is "Blocked" - Review failed dependencies @@ -156,6 +179,7 @@ Build something cool ### Cannot Approve Task **Symptoms:** + - Task shows as "Ready" - Approve button doesn't work - Error when trying to approve @@ -163,18 +187,22 @@ Build something cool **Solutions:** **Check task status is "Ready":** + - Only ready tasks can be approved - Pending/blocked tasks cannot be approved **Verify you own the composite task:** + - Only the user who created it can approve nodes - Check you're logged in correctly **Refresh the page:** + - Status may have changed - Reload to get latest state **Sync composite task:** + - Updates all task statuses - Resolves state inconsistencies @@ -183,6 +211,7 @@ Build something cool ### Auto-Approval Not Working **Symptoms:** + - Auto-approval enabled - Tasks become ready - But not automatically approved/executed @@ -190,17 +219,20 @@ Build something cool **Solutions:** **Verify auto-approval is enabled:** + 1. Go to composite task details 2. Check "Auto-Approval" toggle is ON 3. Re-enable if needed **Sync to trigger auto-approval:** + 1. Click "Sync Composite Task" 2. System detects ready tasks 3. Auto-approves if enabled 4. Spawns unit tasks **Check for errors:** + - Review composite task logs - Look for auto-approval failures - Verify repository connection @@ -208,12 +240,14 @@ Build something cool ### Want to Disable Auto-Approval **How to disable mid-execution:** + 1. Go to composite task details 2. Toggle "Auto-Approval" to OFF 3. Future ready tasks won't auto-execute 4. Currently running tasks continue **Note:** + - Already approved tasks continue running - Only affects tasks that haven't been approved yet @@ -222,11 +256,13 @@ Build something cool ### Cannot Edit Task Prompt **Symptoms:** + - Want to modify task prompt - Edit button disabled or missing - Changes don't save **Possible Causes:** + - Task is in wrong status for editing - Don't have permission - Task already executing @@ -234,15 +270,18 @@ Build something cool **Solutions:** **Check task status:** + - Can edit: `pending`, `ready`, `blocked` - Cannot edit: `approved`, `in_progress`, `completed`, `failed` **For approved tasks:** + - Cannot edit (already executing) - Cancel spawned unit task if needed - Retry the node after failure **For completed/failed tasks:** + - Cannot edit completed work - Can retry failed tasks - Retry creates new unit task @@ -250,6 +289,7 @@ Build something cool ### Retry Not Working **Symptoms:** + - Click "Retry" on failed task - Nothing happens - Task remains failed @@ -257,15 +297,18 @@ Build something cool **Solutions:** **Check if task is actually failed:** + - Status must be "Failed" or "Approved" - Can only retry these statuses **Verify associated unit task:** + - Failed nodes have spawned tasks - Check unit task status - May need to delete unit task first **Sync before retry:** + 1. Sync composite task 2. Verifies current state 3. Then retry the node @@ -273,12 +316,14 @@ Build something cool ### Node Stuck in "Approved" Status **Symptoms:** + - Approved a task - Status is "Approved" - But no unit task spawned - Stays approved indefinitely **Causes:** + - Unit task creation failed - System error during spawn - Connection issue @@ -286,16 +331,19 @@ Build something cool **Solutions:** **Retry the node:** + 1. Click retry on the approved node 2. Creates new unit task 3. Monitors execution **Check error logs:** + - Look for task spawn errors - Verify repository connection - Check workflow execution permissions **Sync composite task:** + - May resolve status issues - Updates task relationships @@ -304,29 +352,34 @@ Build something cool ### Tasks Don't Build on Previous Work **Symptoms:** + - Later tasks don't reference earlier PRs - Work is duplicated - Missing context from dependencies **Cause:** + - System should automatically include PR references - May be a timing issue **Solutions:** **Ensure dependencies are completed:** + - Wait for dependency PRs to merge - System includes PR numbers in prompts - Later tasks reference completed work **Manual context in prompt edit:** When approving a task, edit prompt to add: + ``` Reference the work completed in PR #123 and PR #456. Build upon the authentication system from those PRs. ``` **Check dependency PRs are merged:** + - Dependencies should complete before children - Merged PRs provide context - Open PRs may not provide enough context @@ -334,6 +387,7 @@ Build upon the authentication system from those PRs. ### AI Misunderstands Task Context **Symptoms:** + - Generated code doesn't align with plan - Task seems unrelated to project - Wrong approach taken @@ -341,6 +395,7 @@ Build upon the authentication system from those PRs. **Solutions:** **Edit prompt before approval:** + 1. When task becomes ready 2. Click "Edit Prompt" 3. Add specific context: @@ -351,21 +406,24 @@ Build upon the authentication system from those PRs. ``` **Provide file references:** + ``` Update @src/services/auth.ts to use the new JWT tokens from the authentication task. ``` **Request changes via review:** + - After PR is created - Leave specific guidance -- AutoDev will update +- DevBird will update ## Dependency and Blocking Issues ### Task Blocked by Failed Dependency **Symptoms:** + - Task shows "Blocked" status - Dependency task failed - Cannot proceed @@ -373,12 +431,14 @@ JWT tokens from the authentication task. **Solutions:** **Fix the failed dependency:** + 1. Navigate to failed dependency task 2. Review what went wrong 3. Retry the failed task 4. Once it completes, blocked task becomes ready **Or modify the graph:** + - Delete the blocked task (if not needed) - Create new unit task as workaround - Manually complete the work @@ -386,15 +446,18 @@ JWT tokens from the authentication task. ### Circular Dependency Detected **Symptoms:** + - Some tasks never become ready - Mutual dependencies - Graph seems stuck **This shouldn't happen:** + - Planning should prevent this - DAG validation should catch it **If it does occur:** + 1. Report to support with task details 2. Delete composite task 3. Create new task with clearer prompt @@ -405,6 +468,7 @@ JWT tokens from the authentication task. ### Sync Operation Fails **Symptoms:** + - Click "Sync Composite Task" - Error message appears - No updates occur @@ -412,16 +476,19 @@ JWT tokens from the authentication task. **Solutions:** **Check repository connection:** + 1. Verify repository is connected 2. Check GitHub App is installed 3. Reconnect if needed **Try again:** + - Temporary GitHub API issues - Wait a few minutes - Retry sync operation **Check permissions:** + - Must have repository access - GitHub App needs permissions - Verify in repository settings @@ -429,6 +496,7 @@ JWT tokens from the authentication task. ### Sync Shows Wrong Results **Symptoms:** + - Sync completes - But task statuses still wrong - PRs not reflecting correctly @@ -436,16 +504,19 @@ JWT tokens from the authentication task. **What to check:** **PR merge status in GitHub:** + 1. Go to GitHub repository 2. Check actual PR status -3. Compare with AutoDev display +3. Compare with DevBird display **Wait for GitHub API:** + - GitHub webhooks may be delayed - Wait 1-2 minutes - Retry sync **Force refresh:** + 1. Sync composite task 2. Refresh browser page 3. Check updated statuses @@ -455,11 +526,13 @@ JWT tokens from the authentication task. ### Composite Task Very Slow **Symptoms:** + - Taking days to complete - Many tasks waiting - Progress is slow **Causes:** + 1. Sequential dependencies 2. Waiting for approvals 3. Long-running unit tasks @@ -467,16 +540,19 @@ JWT tokens from the authentication task. **Solutions:** **Enable auto-approval:** + - Eliminates approval delays - Tasks execute immediately when ready - Faster overall completion **Review task graph structure:** + - Too many sequential dependencies? - Could some tasks be parallel? - May need better planning **For future tasks:** + - Provide better context in prompt - AI will optimize parallelization - Reduce sequential dependencies @@ -484,22 +560,26 @@ JWT tokens from the authentication task. ### Too Many Nodes **Symptoms:** + - Composite task created 50+ nodes - Overwhelming to manage - Many small tasks **Cause:** + - AI over-decomposed the project - Prompt was too broad **Solutions:** **For current task:** + - Enable auto-approval to reduce management - Let it run automatically - Monitor progress **For future tasks:** + - Be more specific about scope - Request specific number of major steps - Example: "Break this into 5-8 major tasks" @@ -509,6 +589,7 @@ JWT tokens from the authentication task. ### Cannot Delete Composite Task **Symptoms:** + - Delete button disabled - Error when trying to delete - Task remains @@ -516,33 +597,39 @@ JWT tokens from the authentication task. **Solutions:** **Check for running tasks:** + - Running unit tasks prevent deletion - Wait for completion - Or cancel unit tasks first **Force delete process:** + 1. Delete composite task 2. System cancels incomplete unit tasks 3. Blocks all pending nodes 4. Removes composite task **Verify permissions:** + - Only creator can delete - Check correct user is logged in ### Partial Deletion Issues **Symptoms:** + - Composite task deleted - But some unit tasks remain - PRs still open **This is expected:** + - Unit tasks are preserved for history - PRs remain open (you can close manually) - Task graph is removed **To clean up:** + 1. Close remaining PRs on GitHub 2. Review unit task history if needed 3. Unit tasks show as "Cancelled" @@ -552,6 +639,7 @@ JWT tokens from the authentication task. ### Status Shows Incorrect Progress **Symptoms:** + - Progress shows "3/10 completed" - But more tasks actually done - Counts don't match @@ -559,11 +647,13 @@ JWT tokens from the authentication task. **Solutions:** **Sync composite task:** + - Recalculates progress - Updates node counts - Fixes display **What affects count:** + - Only "Completed" nodes count - Failed nodes don't count as complete - In-progress nodes don't count yet @@ -571,6 +661,7 @@ JWT tokens from the authentication task. ### Task Graph Visualization Not Loading **Symptoms:** + - Graph diagram doesn't appear - Shows loading spinner forever - Blank visualization area @@ -578,15 +669,18 @@ JWT tokens from the authentication task. **Solutions:** **Refresh the page:** + - Browser cache issue - Hard refresh (Ctrl+Shift+R) **Check browser console:** + - Open dev tools (F12) - Look for JavaScript errors - Report if errors found **Try different browser:** + - Temporary browser issue - Test in Chrome/Firefox/Safari @@ -595,6 +689,7 @@ JWT tokens from the authentication task. ### Writing Better Prompts **Include project structure:** + ``` Build a blogging platform with: 1. Backend API (Node.js + Express) @@ -605,12 +700,14 @@ Build a blogging platform with: ``` **Specify technical stack:** + ``` Use TypeScript, follow REST API best practices, include unit tests, and set up CI/CD. ``` **Define clear boundaries:** + ``` Only include core CRUD operations. Do not include admin panel or analytics. @@ -620,16 +717,19 @@ Focus on MVP functionality. ### Monitoring Progress **Use auto-approval wisely:** + - Enable for trusted, well-defined tasks - Disable for complex/critical work - Monitor execution regularly **Review task graph regularly:** + - Check for blocked nodes - Identify failed dependencies - Keep tasks moving forward **Sync periodically:** + - Ensures accurate status - Catches missed updates - Prevents stuck states @@ -637,16 +737,19 @@ Focus on MVP functionality. ### Managing Complexity **Start smaller:** + - First composite task: 5-8 nodes - Build confidence - Scale up gradually **Break mega-projects:** + - Don't try to build entire app in one task - Create multiple composite tasks - Each for a major feature/milestone **Monitor costs:** + - Composite tasks can be expensive - Each node = separate workflow execution - Plan accordingly @@ -658,17 +761,20 @@ Focus on MVP functionality. When reporting composite task issues: 1. **Composite Task Info:** + - Composite task ID - Original prompt - Number of nodes in graph - Current status 2. **Problematic Nodes:** + - Node IDs having issues - Node statuses - Dependencies 3. **Spawned Tasks:** + - Unit task IDs - Their statuses - PR numbers @@ -687,6 +793,6 @@ When reporting composite task issues: ## Next Steps -- [Unit Task Troubleshooting](/autodev/troubleshooting/unit-task) -- [Understanding Composite Tasks](/autodev/tasks/composite) -- [Task Graph Best Practices](/autodev/tasks/composite#task-graph-best-practices) +- [Unit Task Troubleshooting](/devbird/troubleshooting/unit-task) +- [Understanding Composite Tasks](/devbird/tasks/composite) +- [Task Graph Best Practices](/devbird/tasks/composite#task-graph-best-practices) diff --git a/autodev/troubleshooting/pr-reviews.mdx b/devbird/troubleshooting/pr-reviews.mdx similarity index 82% rename from autodev/troubleshooting/pr-reviews.mdx rename to devbird/troubleshooting/pr-reviews.mdx index 63f3f33..7b7cd5b 100644 --- a/autodev/troubleshooting/pr-reviews.mdx +++ b/devbird/troubleshooting/pr-reviews.mdx @@ -1,24 +1,27 @@ --- title: "PR Review Troubleshooting" -description: "Common issues and solutions for AutoDev pull request reviews" +description: "Common issues and solutions for DevBird pull request reviews" --- ## PR stuck in draft **Symptoms:** + - PR remains in draft status - All checks passing but not ready for review - Cannot merge PR **Solution:** + 1. Check CI status - ensure all checks are passing -2. Verify auto-undraft is enabled in [Settings](/autodev/settings) +2. Verify auto-undraft is enabled in [Settings](/devbird/settings) 3. Manually undraft the PR if needed 4. Check if there are pending review comments -## AutoDev not responding to reviews +## DevBird not responding to reviews **Symptoms:** + - Reviewer submitted feedback - No workflow triggered - PR not updated @@ -26,7 +29,8 @@ description: "Common issues and solutions for AutoDev pull request reviews" - No response to feedback **Possible causes:** -- Reviewer hasn't connected the repository in AutoDev + +- Reviewer hasn't connected the repository in DevBird - Bot reviews with auto-apply disabled - GitHub webhook not configured or delivery failing - Review was a simple approval (doesn't trigger workflow) @@ -36,32 +40,37 @@ description: "Common issues and solutions for AutoDev pull request reviews" **Solution:** **Ensure reviewer has repository access:** -1. Reviewer must connect the repository in AutoDev + +1. Reviewer must connect the repository in DevBird 2. Verify repository appears in reviewer's dashboard -3. Check that AutoDev GitHub App is installed +3. Check that DevBird GitHub App is installed **Enable auto-apply for bot reviews:** -See [Auto-apply Bot Reviews](/autodev/settings#auto-apply-bot-reviews) in the settings documentation for details on enabling this feature. +See [Auto-apply Bot Reviews](/devbird/settings#auto-apply-bot-reviews) in the settings documentation for details on enabling this feature. **Verify webhook configuration:** + 1. Repository settings → Webhooks -2. Check AutoDev webhook exists +2. Check DevBird webhook exists 3. Verify webhook is active 4. Check recent delivery status **Check GitHub webhook logs:** + 1. Go to repository settings on GitHub 2. Navigate to Webhooks -3. Find AutoDev webhook +3. Find DevBird webhook 4. Check recent deliveries for errors 5. Redeliver failed webhooks if needed **Check review type:** + - Simple approvals don't trigger workflows - Comments must be submitted with "Request changes" or "Comment" - Verify review was actually submitted (not just comment) **Manual trigger:** + 1. Go to task details 2. Click "Update PR" 3. Enter update instructions @@ -70,36 +79,42 @@ See [Auto-apply Bot Reviews](/autodev/settings#auto-apply-bot-reviews) in the se ## CI fixes not working **Symptoms:** + - CI checks failing -- AutoDev not attempting fixes +- DevBird not attempting fixes - PR remains with failed checks **Possible causes:** + - Already attempted fix for this commit (rate limited) - Workflow execution failed - GitHub Actions quota exceeded -- AutoDev webhook not receiving check events +- DevBird webhook not receiving check events **Solution:** **Push new commit to allow new fix attempt:** + ```bash git commit --allow-empty -m "Trigger CI fix attempt" git push ``` **Check workflow execution logs:** + 1. Go to task details page 2. Find workflow executions 3. Look for "ci_fix" type workflows 4. Review error messages **Verify GitHub Actions quota:** + 1. Check repository Actions tab 2. Verify workflows can run 3. Check organization billing if quota exceeded **Manual fix alternative:** + 1. Review CI failure logs 2. Make fixes locally 3. Push updates to PR branch @@ -107,12 +122,14 @@ git push ## Too many automated updates **Symptoms:** + - PR receives excessive updates - Multiple workflow runs - High costs - Reviewers confused by constant changes **Causes:** + - Task prompt too vague - Review feedback unclear - Multiple bots triggering updates @@ -121,11 +138,13 @@ git push **Solution:** **Break tasks into smaller units:** + - Create focused, single-purpose tasks - Avoid complex multi-step tasks - Use composite tasks for large projects **Be more specific in initial prompt:** + ``` Good: Fix null pointer exception in UserService.authenticateUser() when email field is missing @@ -134,18 +153,20 @@ Bad: Fix the bug ``` **Manually review and update PRs:** + 1. Disable auto-apply temporarily 2. Review accumulated feedback 3. Make consolidated updates 4. Re-enable auto-apply **Limit bot reviews:** + 1. Configure bots to review less frequently 2. Adjust bot sensitivity 3. Use auto-apply selectively ## Next steps -- [PR Review Process](/autodev/reviewing-prs) -- [Unit Task Troubleshooting](/autodev/troubleshooting/unit-task) -- [Composite Task Troubleshooting](/autodev/troubleshooting/composite-task) +- [PR Review Process](/devbird/reviewing-prs) +- [Unit Task Troubleshooting](/devbird/troubleshooting/unit-task) +- [Composite Task Troubleshooting](/devbird/troubleshooting/composite-task) diff --git a/autodev/troubleshooting/unit-task.mdx b/devbird/troubleshooting/unit-task.mdx similarity index 90% rename from autodev/troubleshooting/unit-task.mdx rename to devbird/troubleshooting/unit-task.mdx index 5a8294f..204e6ff 100644 --- a/autodev/troubleshooting/unit-task.mdx +++ b/devbird/troubleshooting/unit-task.mdx @@ -4,21 +4,24 @@ description: "Common issues with unit tasks and how to resolve them" --- -This document is still under review. The content may be inaccurate or outdated. + This document is still under review. The content may be inaccurate or + outdated. -This guide helps you troubleshoot common issues with unit tasks in AutoDev. +This guide helps you troubleshoot common issues with unit tasks in DevBird. ## Task Creation Issues ### Task Not Starting **Symptoms:** + - Task stuck in "Pending" status - No workflow execution visible in GitHub Actions - Task created but nothing happens **Possible Causes:** + 1. Workflow file missing or incorrect 2. GitHub Actions disabled 3. Repository not properly connected @@ -27,25 +30,29 @@ This guide helps you troubleshoot common issues with unit tasks in AutoDev. **Solutions:** **Check workflow file exists:** + ```bash # Verify file exists -ls .github/workflows/autodev.yml +ls .github/workflows/devbird.yml # Check file is on default branch git branch --show-current ``` **Verify GitHub Actions is enabled:** + 1. Go to repository Settings 2. Navigate to Actions → General 3. Ensure "Allow all actions and reusable workflows" is selected **Reconnect repository:** -1. AutoDev → Repositories + +1. DevBird → Repositories 2. Find your repository 3. Click "Disconnect" then "Reconnect" **Manually retry:** + 1. Go to task details page 2. Click "Retry Task" button 3. Check workflow execution logs @@ -53,11 +60,13 @@ git branch --show-current ### Invalid Configuration Error **Symptoms:** + - Task fails immediately - Error: "Invalid agent configuration" - Workflow execution shows configuration error **Possible Causes:** + 1. AI agent API key not set 2. Invalid agent type specified 3. Model type not supported @@ -65,15 +74,18 @@ git branch --show-current **Solutions:** **Verify API key:** + 1. Repository Settings → Secrets → Actions 2. Check required secret exists (e.g., `ANTHROPIC_API_KEY`) 3. Regenerate key if needed **Check agent configuration:** -- Agent type must be one of the [supported AI agents](/autodev/getting-started/ai-agent) + +- Agent type must be one of the [supported AI agents](/devbird/getting-started/ai-agent) - Model type must match agent's supported models **Use default settings:** + - Leave agent/model fields empty to use team defaults - Verify team defaults in Settings page @@ -82,6 +94,7 @@ git branch --show-current ### Workflow Fails to Trigger **Symptoms:** + - Task status changes to "In Progress" but no GitHub Actions run - No workflow run visible in Actions tab - Task eventually times out @@ -89,6 +102,7 @@ git branch --show-current **Solutions:** **Check workflow permissions:** + ```yaml permissions: id-token: write @@ -98,21 +112,24 @@ permissions: ``` **Verify workflow dispatch event:** + ```yaml on: - workflow_dispatch: # Must be present + workflow_dispatch: # Must be present inputs: - autodev_task_token: + devbird_task_token: required: true ``` **Check GitHub API status:** + - Visit [githubstatus.com](https://www.githubstatus.com) - Look for API or Actions outages ### Workflow Hangs or Timeouts **Symptoms:** + - Workflow runs for extended period - Eventually times out (2+ hours) - No progress updates @@ -120,18 +137,21 @@ on: **Solutions:** **Add timeout to workflow:** + ```yaml jobs: - autodev: + devbird: runs-on: ubuntu-latest - timeout-minutes: 60 # 1 hour max + timeout-minutes: 60 # 1 hour max ``` **Check runner availability:** + - If using self-hosted runners, verify they're online - Switch to GitHub-hosted runners temporarily **Simplify the task:** + - Break large task into smaller pieces - Reduce scope of changes requested - Be more specific in prompt @@ -139,6 +159,7 @@ jobs: ### Authentication Errors **Symptoms:** + - Error: "Authentication failed" - Error: "Invalid task token" - Workflow fails at authentication step @@ -146,20 +167,23 @@ jobs: **Solutions:** **Verify OIDC is configured:** + ```yaml permissions: - id-token: write # Required for OIDC + id-token: write # Required for OIDC ``` **Check task token is passed:** + ```yaml -- uses: delino-io/autodev-action@v1 +- uses: delino-io/devbird-action@v1 with: - task_token: ${{ inputs.autodev_task_token }} # Must be present + task_token: ${{ inputs.devbird_task_token }} # Must be present ``` **Repository must be connected:** -1. Verify repository appears in AutoDev + +1. Verify repository appears in DevBird 2. Status should be "Connected" 3. Reconnect if needed @@ -168,11 +192,13 @@ permissions: ### No PRs Created **Symptoms:** + - Task completes successfully - Status changes to "Completed" - But no pull requests appear **Possible Causes:** + 1. AI determined no changes were needed 2. Changes were made but no branches registered 3. PR creation failed silently @@ -180,26 +206,30 @@ permissions: **Solutions:** **Check workflow logs:** + 1. Go to GitHub Actions 2. Find the workflow run 3. Look for "Creating pull request" steps 4. Check for any errors **Verify task prompt was clear:** + - Was the request specific enough? - Did you specify what to create/change? - Try rephrasing and creating new task **Check branch was created:** + ```bash # List all branches git branch -a -# Look for autodev-* branches -git branch -a | grep autodev +# Look for devbird-* branches +git branch -a | grep devbird ``` **Task may have legitimately completed without changes:** + - AI analyzed request - Determined changes weren't needed - This is normal behavior for some prompts @@ -207,24 +237,28 @@ git branch -a | grep autodev ### PR Created on Wrong Branch **Symptoms:** + - PR targets wrong base branch - Changes based on wrong branch **Solutions:** **Specify base branch when creating task:** + 1. In task creation form 2. Expand "Advanced Settings" 3. Set "Base Branch" to desired branch (e.g., "develop") **Update workflow default:** + ```yaml base_branch: required: false - default: 'develop' # Change from 'main' + default: "develop" # Change from 'main' ``` **For existing PR:** + - You can change the base branch on GitHub - Go to PR → Click "Edit" near title - Change base branch in dropdown @@ -232,21 +266,25 @@ base_branch: ### Multiple Unwanted PRs **Symptoms:** + - Task creates too many PRs - PRs are fragmented - Changes should be in one PR **Cause:** + - AI decided to split changes across multiple PRs - This is sometimes intentional for large changes **Solutions:** **For future tasks:** + - Add to prompt: "Create all changes in a single PR" - Be more specific about scope **For existing PRs:** + - Manually merge the branches - Close extra PRs - Keep the main one @@ -256,23 +294,27 @@ base_branch: ### Generated Code Doesn't Compile **Symptoms:** + - CI checks fail - Code has syntax errors - Build fails **Solutions:** -**Let AutoDev auto-fix:** +**Let DevBird auto-fix:** + - Wait for automatic CI fix workflow -- AutoDev detects failures and attempts fixes +- DevBird detects failures and attempts fixes - Usually completes in 5-10 minutes **Provide feedback via review:** + 1. Leave review comment on specific lines 2. Request changes -3. AutoDev will update the code +3. DevBird will update the code **Manual update request:** + 1. Go to task details 2. Click "Update PR" 3. Provide specific fix instructions @@ -280,6 +322,7 @@ base_branch: ### Code Doesn't Match Requirements **Symptoms:** + - Code works but doesn't do what you wanted - Missing features - Wrong approach @@ -287,17 +330,20 @@ base_branch: **Solutions:** **Review and request changes:** + 1. Leave detailed review comments 2. Explain what's wrong and what you expected 3. Request changes on GitHub PR -4. AutoDev will address feedback +4. DevBird will address feedback **Update the PR:** + 1. Task details → Update PR 2. Provide additional context 3. Clarify requirements **Create new task:** + - If changes are too different - Delete current task - Create new task with clearer prompt @@ -305,6 +351,7 @@ base_branch: ### Code Style Doesn't Match Project **Symptoms:** + - Code formatting is different - Naming conventions don't match - Structure is inconsistent @@ -312,15 +359,18 @@ base_branch: **Solutions:** **Request style fixes:** + - Leave review comment - Reference your style guide - Example: "Please follow naming conventions in @CONTRIBUTING.md" **Set up linters:** + - Add ESLint, Prettier, or other formatters to CI -- AutoDev will see failures and auto-fix +- DevBird will see failures and auto-fix **Improve future prompts:** + ``` Follow the code style in @src/services/example.ts Use the same patterns as existing services @@ -331,6 +381,7 @@ Use the same patterns as existing services ### Task Stuck "In Progress" **Symptoms:** + - Task has been "In Progress" for hours/days - Workflow completed but status didn't update - PRs are created but task status unchanged @@ -338,16 +389,19 @@ Use the same patterns as existing services **Solutions:** **Sync task status:** + 1. Go to task details page 2. Click "Sync Task" (in debug/actions menu) -3. AutoDev checks PR status and updates task +3. DevBird checks PR status and updates task **Check workflow execution:** + - Look at workflow execution history - See if workflow actually completed - Check for errors in logs **Manual status check:** + - If all PRs are merged → Task should be "Completed" - If PRs are closed without merge → Task should be "Failed" - Sync operation will fix this @@ -355,6 +409,7 @@ Use the same patterns as existing services ### Task Status Incorrect **Symptoms:** + - Task shows "Completed" but PRs still open - Task shows "Failed" but PRs are merged - Status doesn't reflect reality @@ -362,12 +417,14 @@ Use the same patterns as existing services **Solution:** **Use Sync Task feature:** + 1. Task details page 2. Sync Task button 3. Checks GitHub for actual PR status 4. Updates task status accordingly **What Sync does:** + - Fetches latest PR data from GitHub - Checks merge status - Updates CI check status @@ -376,6 +433,7 @@ Use the same patterns as existing services ### Cannot Delete Task **Symptoms:** + - Delete button doesn't work - Error when trying to delete - Task remains after delete attempt @@ -383,28 +441,33 @@ Use the same patterns as existing services **Solutions:** **Check permissions:** + - Only task creator can delete - Verify you're logged in as correct user **Task may be running:** + - Wait for workflow to complete - Cancel workflow first, then delete **Force delete:** + 1. Close all PRs manually on GitHub 2. Wait a few seconds -3. Retry delete in AutoDev +3. Retry delete in DevBird ## Performance Issues ### Task Takes Too Long **Symptoms:** + - Task runs for 30+ minutes - Much slower than expected - Workflow seems stuck **Possible Causes:** + 1. Large codebase 2. Complex task 3. Slow AI agent response @@ -413,16 +476,19 @@ Use the same patterns as existing services **Solutions:** **Break into smaller tasks:** + - Split large request into focused tasks - Each task completes faster - Better for tracking progress **Use faster agent/model:** + - Switch to GPT-3.5 or Claude Haiku - Faster response times - Trade quality for speed **Optimize workflow:** + - Remove unnecessary setup steps - Cache dependencies - Use faster runner (self-hosted) @@ -430,6 +496,7 @@ Use the same patterns as existing services ### Rate Limit Errors **Symptoms:** + - Error: "Rate limit exceeded" - Task fails with 429 error - API quota exceeded @@ -437,11 +504,13 @@ Use the same patterns as existing services **Solutions:** **For GitHub API limits:** + - Wait an hour for reset - Reduce concurrent tasks - Use GitHub App authentication (automatic) **For AI provider limits:** + - Check provider dashboard for quota - Upgrade API plan - Wait for rate limit reset @@ -453,20 +522,22 @@ Use the same patterns as existing services 1. Go to repository on GitHub 2. Click "Actions" tab -3. Find "AutoDev" workflow +3. Find "DevBird" workflow 4. Click on the specific run 5. Click on job name to see logs ### Important Log Sections **Authentication:** + ``` -Authenticating with AutoDev... +Authenticating with DevBird... ✓ Task token validated ✓ OIDC token exchanged ``` **Agent Execution:** + ``` Running Claude Code... Analyzing codebase... @@ -474,28 +545,33 @@ Generating changes... ``` **PR Creation:** + ``` Creating pull request... -✓ Branch created: autodev-task-123 +✓ Branch created: devbird-task-123 ✓ PR #456 created ``` ### Common Error Messages **"No ANTHROPIC_API_KEY found"** + - API key not set in repository secrets - Add secret and retry task **"Branch already exists"** + - Previous task created same branch - Delete branch on GitHub - Retry task **"Permission denied"** + - Workflow permissions missing - Add required permissions to workflow file **"Task token invalid"** + - Task may have been deleted - Try creating new task - Check repository is connected @@ -507,17 +583,20 @@ Creating pull request... When requesting support, include: 1. **Task Details:** + - Task ID - Repository name - Task prompt - Agent and model used 2. **Workflow Information:** + - GitHub Actions run URL - Workflow logs (relevant sections) - Error messages 3. **PR Information:** + - PR numbers created - PR status - Review comments @@ -536,6 +615,7 @@ When requesting support, include: ## Prevention Tips ### Write Clear Prompts + ``` ✓ Good: "Fix null pointer exception in UserService.java line 45 when email is empty. Add validation and return 400 error." @@ -544,22 +624,25 @@ When requesting support, include: ``` ### Test Incrementally + - Start with simple tasks - Verify each task works - Build confidence before complex tasks ### Monitor Costs + - Track workflow execution count - Monitor AI provider usage - Set up usage alerts ### Regular Maintenance + - Keep workflow file updated - Rotate API keys periodically - Review and clean up old tasks ## Next Steps -- [Composite Task Troubleshooting](/autodev/troubleshooting/composite-task) -- [PR Review Process](/autodev/reviewing-prs) -- [AI Agent Configuration](/autodev/getting-started/ai-agent) +- [Composite Task Troubleshooting](/devbird/troubleshooting/composite-task) +- [PR Review Process](/devbird/reviewing-prs) +- [AI Agent Configuration](/devbird/getting-started/ai-agent) diff --git a/docs.json b/docs.json index 508242a..2639656 100644 --- a/docs.json +++ b/docs.json @@ -15,78 +15,90 @@ "groups": [ { "group": "Getting started", - "pages": ["index"] + "pages": [ + "index" + ] }, { "group": "Authentication", - "pages": ["core/api-keys/creation"] + "pages": [ + "core/api-keys/creation" + ] }, { "group": "Teams", - "pages": ["core/teams/creation"] + "pages": [ + "core/teams/creation" + ] } ] }, { - "tab": "AutoDev", + "tab": "DevBird", "groups": [ { "group": "Getting started", "pages": [ - "autodev/index", - "autodev/comparison", - "autodev/getting-started/prerequisites", - "autodev/getting-started/github-app", - "autodev/getting-started/github-workflow", - "autodev/getting-started/ai-agent", - "autodev/getting-started/first-pr" + "devbird/index", + "devbird/comparison", + "devbird/getting-started/prerequisites", + "devbird/getting-started/github-app", + "devbird/getting-started/github-workflow", + "devbird/getting-started/ai-agent", + "devbird/getting-started/first-pr" ] }, { "group": "Managing Tasks", "pages": [ - "autodev/tasks/index", - "autodev/tasks/unit/index", - "autodev/tasks/composite/index" + "devbird/tasks/index", + "devbird/tasks/unit/index", + "devbird/tasks/composite/index" ] }, { "group": "Settings", - "pages": ["autodev/settings/index"] + "pages": [ + "devbird/settings/index" + ] }, { "group": "Configuring AI Agents", "pages": [ - "autodev/ai-agents/claude-code", - "autodev/ai-agents/codex-cli", - "autodev/ai-agents/opencode", - "autodev/ai-agents/gemini-cli", - "autodev/ai-agents/crush-cli", - "autodev/ai-agents/github-copilot-cli" + "devbird/ai-agents/claude-code", + "devbird/ai-agents/codex-cli", + "devbird/ai-agents/opencode", + "devbird/ai-agents/gemini-cli", + "devbird/ai-agents/crush-cli", + "devbird/ai-agents/github-copilot-cli" ] }, { "group": "Architecture", - "pages": ["autodev/architecture/webhook"] + "pages": [ + "devbird/architecture/webhook" + ] }, { "group": "Cost reduction (optional)", - "pages": ["autodev/cost-reduction/github-runner"] + "pages": [ + "devbird/cost-reduction/github-runner" + ] }, { "group": "Reviewing PRs", "pages": [ - "autodev/reviewing-prs/index", - "autodev/reviewing-prs/ai-reviewer" + "devbird/reviewing-prs/index", + "devbird/reviewing-prs/ai-reviewer" ] }, { "group": "Troubleshooting", "pages": [ - "autodev/troubleshooting/unit-task", - "autodev/troubleshooting/composite-task", - "autodev/troubleshooting/pr-reviews", - "autodev/troubleshooting/ai-reviewer" + "devbird/troubleshooting/unit-task", + "devbird/troubleshooting/composite-task", + "devbird/troubleshooting/pr-reviews", + "devbird/troubleshooting/ai-reviewer" ] } ] @@ -142,5 +154,11 @@ "domain": "docs.delino.io", "server": "plausible.internal.delino.io" } - } -} + }, + "redirects": [ + { + "source": "/devbird/:path*", + "destination": "/devbird/:path*" + } + ] +} \ No newline at end of file