doc(devbird): Add some docs

devbird/getting-started/github-workflow.mdx

@@ -153,6 +153,26 @@ git commit -m "Add DevBird workflow"
 git push
 ```
 
+## Understanding workflow execution
+
+<Info>
+**Important: Workflow runs on the main branch**
+
+For security reasons, the DevBird GitHub Action always executes on your repository's default branch (typically `main`). This means:
+
+- The workflow runs from the main branch codebase
+- GitHub Actions logs will show the workflow running on `main`
+- This is by design to prevent security vulnerabilities
+
+The `base_branch` parameter controls which branch DevBird uses as the base when creating new feature branches, but the workflow execution itself always happens on the default branch.
+</Info>
+
+This security design prevents potential issues such as:
+
+- Malicious workflow modifications in feature branches
+- Unauthorized access to repository secrets
+- Tampering with the DevBird workflow configuration
+
 ## Next steps
 
 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.

devbird/reviewing-prs/index.mdx

@@ -54,6 +54,17 @@ When everything passes:
 - PR is automatically undrafted (if enabled)
 - Ready for final approval and merge
 
+## Multiple concurrent PRs
+
+DevBird may create multiple pull requests simultaneously for different tasks. This is expected behavior.
+
+Each PR:
+- Represents a separate task or feature
+- Can be reviewed independently
+- Should be merged individually after approval
+
+Simply review and merge each PR based on its own merits, in any order that makes sense for your workflow.
+
 ## PR comments
 
 ### Task Link Comment

devbird/tasks/composite/index.mdx

@@ -16,6 +16,10 @@ When you create a composite task:
 - Tasks are organized with dependencies
 - Plan is saved for your review
 
+<Note>
+**Simple tasks can have a single node**: For straightforward requests that don't require breaking down into multiple steps, the AI may generate a task graph with just one node. This is normal and expected for tasks that are simple enough to be completed in a single execution.
+</Note>
+
 Status: **Planning**
 
 ### 2. Review and Start