feat: Rename Integrations Tab label to Deploy

[milovate]

Q/A checklist

• I have tested my UI changes on mobile and they look acceptable
• I have tested changes to the workflows in both the API and the UI
• I have done a code review of my changes and looked at each line of the diff + the references of each function I have changed
• My changes have not increased the import time of the server

How to check import time?

time python -c 'import server'

You can visualize this using tuna:

python3 -X importtime -c 'import server' 2> out.log && tuna out.log

To measure import time for a specific library:

$ time python -c 'import pandas'

________________________________________________________
Executed in    1.15 secs    fish           external
   usr time    2.22 secs   86.00 micros    2.22 secs
   sys time    0.72 secs  613.00 micros    0.72 secs

To reduce import times, import libraries that take a long time inside the functions that use them instead of at the top of the file:

def my_function():
    import pandas as pd
    ...

Legal Boilerplate

Look, I get it. The entity doing business as “Gooey.AI” and/or “Dara.network” was incorporated in the State of Delaware in 2020 as Dara Network Inc. and is gonna need some rights from me in order to utilize my contributions in this PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Dara Network Inc can use, modify, copy, and redistribute my contributions, under its choice of terms.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request renames user-facing references from "Integrations" to "Deploy" or "Deployments" across multiple modules. Changes are text-only except for a small breadcrumb conditional: when the current tab equals RecipeTabs.integrations, the breadcrumb prefix becomes "Deployments". Files updated include UI copy, a JS comment in an example generator, error message text, API field descriptions, and the RecipeTabs.integrations title/label.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Multiple, similar textual updates across several files (low individual complexity).
• One small logic change in breadcrumbs increases cognitive load.
• Review should confirm UI wording consistency and that tab label change doesn’t affect routing.

Areas requiring attention:

• daras_ai_v2/breadcrumbs.py: verify the tab comparison and "Deployments" prefix behavior.
• routers/root.py: confirm the RecipeTabs.integrations title/label change is consistent and doesn't break UI rendering.
• routers/bots_api.py and routers/broadcast_api.py: ensure API field description updates are appropriate.
• recipes/VideoBots.py and recipes/VideoBotsStats.py: verify all user-facing strings updated and button/anchor labels remain consistent.

Possibly related PRs

• feat: render web widget on copilot #662 — modifies the same RecipeTabs.integrations title/html and related UI text.
• Header layout changes #732 — related breadcrumb/title rendering changes including integrations/deploy labeling.
• preview tab for copilot #726 — also updates RecipeTabs.integrations tab title/label.

Suggested reviewers

• devxpy

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The PR title "feat: Rename Integrations Tab label to Deploy" directly and accurately summarizes the primary change in the changeset. The raw summary shows that the pull request consistently renames "Integrations" references to "Deploy" across multiple files, including tab labels, UI copy, breadcrumb labels, and API field descriptions. The title is concise, clear, and specific enough that a teammate reviewing the commit history would immediately understand the core objective without confusion.
Description Check	✅ Passed	The PR description exactly matches the required template structure with all sections present and properly completed. It includes the full Q/A checklist with all four items, the complete "How to check import time?" collapsible section with all specified commands and examples, and the legal boilerplate intact. Although the checklist items are unchecked, the template structure itself is fully followed and no required information is missing.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch integrations-name-change

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 74a6cb2 and 7d04dda.

📒 Files selected for processing (8)

• daras_ai_v2/api_examples_widget.py (1 hunks)
• daras_ai_v2/bots.py (1 hunks)
• daras_ai_v2/breadcrumbs.py (1 hunks)
• recipes/VideoBots.py (3 hunks)
• recipes/VideoBotsStats.py (3 hunks)
• routers/bots_api.py (1 hunks)
• routers/broadcast_api.py (1 hunks)
• routers/root.py (1 hunks)

✅ Files skipped from review due to trivial changes (2)

• daras_ai_v2/bots.py
• daras_ai_v2/api_examples_widget.py

🚧 Files skipped from review as they are similar to previous changes (2)

• routers/bots_api.py
• recipes/VideoBotsStats.py

🧰 Additional context used

🧬 Code graph analysis (1)

daras_ai_v2/breadcrumbs.py (1)

routers/root.py (1)

• RecipeTabs (881-925)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: test (3.10.12, 1.8.3)

🔇 Additional comments (6)

daras_ai_v2/breadcrumbs.py (1)

99-99: LGTM! Breadcrumb prefix correctly updated to Deploy terminology.

The conditional logic appropriately uses "Deployments" (plural) for the breadcrumb prefix when viewing the integrations tab, while maintaining the original logic for other tabs.

recipes/VideoBots.py (3)

1616-1616: LGTM! Caption correctly updated to Deploy terminology.

The message appropriately uses "Deployments" (plural) when referring to the collection of deployment configurations, consistent with the breadcrumb naming convention.

---

1645-1650: LGTM! UI labels updated to Deploy terminology.

The label and button text have been appropriately updated from "Integration" to "Deploy"/"Configure" terminology, making the user flow clearer.

---

2075-2079: LGTM! Section heading and link text updated to Deploy terminology.

Both the heading and anchor text correctly use "Deployment" terminology, maintaining consistency with the overall rename.

routers/broadcast_api.py (1)

45-45: LGTM! API documentation updated to reference Deploy tab.

The field description correctly references the new "Deploy" tab name, ensuring API documentation remains consistent with the UI changes.

routers/root.py (1)

908-909: LGTM! Tab title and label updated to Deploy terminology.

The RecipeTabs.integrations enum values have been correctly updated to use "Deploy" terminology while preserving the route name (integrations_route) for backward compatibility. The title includes the appropriate icon and the label is concise.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}