mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-01 13:18:10 +00:00
* feat: adopt directory-based docs versioning with Edge channel Switch docs.crewai.com from navigation-only versioning (every version selector entry rendered the same docs/<lang>/* source files) to Mintlify's directory-based versioning so each version selector entry renders its own snapshot. Add an "Edge" channel under docs/edge/<lang>/* that always reflects main HEAD for unreleased work, eliminating pre-release leakage onto frozen release labels. External links to canonical /<lang>/* URLs are preserved via wildcard redirects that always land on the current default version. Layout: - docs/edge/<lang>/* rolling source (you edit here) - docs/edge/enterprise-api.*.yaml - docs/v<X.Y.Z>/<lang>/* frozen, immutable snapshots - docs/v<X.Y.Z>/enterprise-api.*.yaml - docs/images/ shared, append-only - docs/docs.json nav + redirects URLs follow the Mintlify-idiomatic shape: /edge/<lang>/<page> for Edge, /v<X.Y.Z>/<lang>/<page> for every frozen snapshot. The wildcard redirects /<lang>/:slug* -> /<default>/<lang>/:slug* keep stale links working, and every freeze rewrites them (plus all per-section/per-page redirects) so destinations always resolve to the current default without depending on a second redirect hop. Release flow integration (devtools release): - New module crewai_devtools.docs_versioning.freeze() materialises docs/v<X.Y.Z>/ from docs/edge/, rewrites openapi: refs inside the snapshot, inserts the version into every language block in docs.json, and refreshes all redirect destinations. - _update_docs_and_create_pr() in cli.py now calls that freeze during Phase 2 of devtools release. Edge changelogs are updated first (so the snapshot freeze picks them up), then the snapshot is staged alongside docs.json, branched as docs/freeze-v<X.Y.Z>, and the PR is titled [docs-freeze] docs: snapshot and changelog for v<X.Y.Z> — the title prefix the new CI guard reads. - The PR still gates tag, GitHub release, PyPI publish, and the enterprise release as before; no new PRs are added. - Pre-releases (1.X.YaN, 1.X.YbN, ...) skip the snapshot — they ride Edge — and the docs PR title omits the [docs-freeze] prefix. - docs_check (AI-generated docs scaffolding) writes to docs/edge/<lang>/* so newly-generated unreleased docs land in Edge and never accidentally touch a frozen snapshot. Migration scripts (one-shot): - scripts/docs/freeze_historical_versions.py reconstructs all 16 historical snapshots (v1.10.0 .. v1.14.7) from git tags via git archive | tar, rewriting openapi: MDX refs so each snapshot reads its own enterprise-api YAML rather than the live one. - scripts/docs/prefix_version_paths.py one-shot-migrates docs.json: rewrites every page path in 16 versioned blocks to point under docs/v<X.Y.Z>/, inserts a new Edge entry per language, tags v1.14.7 as Latest (default), prunes pages whose target file doesn't exist in the snapshot (e.g. docs/ar/ didn't exist before v1.12.0), and writes the wildcard + per-section redirects. - scripts/docs/freeze_current_edge.py is now a thin CLI wrapper around docs_versioning.freeze for manual one-off freezes (e.g. retroactively snapshotting a forgotten release). CI guards (.github/workflows/docs-snapshots.yml): - Frozen snapshots under docs/v[0-9]*/ are immutable; only PRs whose title contains [docs-freeze] (i.e. release-cut PRs generated by devtools release or the manual wrapper) may modify them. - Images under docs/images/ are append-only since snapshots share a single image directory. Deleting or renaming an image breaks every historical snapshot that still references it. Restored docs/images/crewai-otel-export.png from PR #3673; it was deleted in PR #4908 but v1.10.0 / v1.10.1 snapshots still reference it. Restoring instead of editing the snapshots preserves historical rendering fidelity and validates the new append-only rule retroactively. Tests: - lib/devtools/tests/test_docs_versioning.py covers the freeze: file copy, openapi rewrite, version insertion, default demotion, redirect upserts, per-section redirect rewriting, idempotency, and invalid inputs. Verified locally with mintlify broken-links: 0 broken links across the full site (Edge + 16 frozen versions, 4 locales). AGENTS.md (repo root) is the contributor guide for the new model; RELEASING.md is the release-cut runbook; README's Contribution section links to both. Co-authored-by: Cursor <cursoragent@cursor.com> * style: resolve linter issues --------- Co-authored-by: Cursor <cursoragent@cursor.com>
90 lines
2.7 KiB
Plaintext
90 lines
2.7 KiB
Plaintext
---
|
|
title: 조건부 태스크
|
|
description: crewAI kickoff에서 조건부 태스크를 사용하는 방법을 알아보세요
|
|
icon: diagram-subtask
|
|
mode: "wide"
|
|
---
|
|
|
|
## 소개
|
|
|
|
crewAI의 조건부 작업(Conditional Tasks)은 이전 작업의 결과에 따라 동적으로 워크플로우를 조정할 수 있도록 합니다.
|
|
이 강력한 기능을 통해 crew는 선택적으로 결정을 내리고 작업을 수행할 수 있어, AI 기반 프로세스의 유연성과 효율성이 향상됩니다.
|
|
|
|
## 예제 사용법
|
|
|
|
```python Code
|
|
from typing import List
|
|
from pydantic import BaseModel
|
|
from crewai import Agent, Crew
|
|
from crewai.tasks.conditional_task import ConditionalTask
|
|
from crewai.tasks.task_output import TaskOutput
|
|
from crewai.task import Task
|
|
from crewai_tools import SerperDevTool
|
|
|
|
# Define a condition function for the conditional task
|
|
# If false, the task will be skipped, if true, then execute the task.
|
|
def is_data_missing(output: TaskOutput) -> bool:
|
|
return len(output.pydantic.events) < 10 # this will skip this task
|
|
|
|
# Define the agents
|
|
data_fetcher_agent = Agent(
|
|
role="Data Fetcher",
|
|
goal="Fetch data online using Serper tool",
|
|
backstory="Backstory 1",
|
|
verbose=True,
|
|
tools=[SerperDevTool()]
|
|
)
|
|
|
|
data_processor_agent = Agent(
|
|
role="Data Processor",
|
|
goal="Process fetched data",
|
|
backstory="Backstory 2",
|
|
verbose=True
|
|
)
|
|
|
|
summary_generator_agent = Agent(
|
|
role="Summary Generator",
|
|
goal="Generate summary from fetched data",
|
|
backstory="Backstory 3",
|
|
verbose=True
|
|
)
|
|
|
|
class EventOutput(BaseModel):
|
|
events: List[str]
|
|
|
|
task1 = Task(
|
|
description="Fetch data about events in San Francisco using Serper tool",
|
|
expected_output="List of 10 things to do in SF this week",
|
|
agent=data_fetcher_agent,
|
|
output_pydantic=EventOutput,
|
|
)
|
|
|
|
conditional_task = ConditionalTask(
|
|
description="""
|
|
Check if data is missing. If we have less than 10 events,
|
|
fetch more events using Serper tool so that
|
|
we have a total of 10 events in SF this week..
|
|
""",
|
|
expected_output="List of 10 Things to do in SF this week",
|
|
condition=is_data_missing,
|
|
agent=data_processor_agent,
|
|
)
|
|
|
|
task3 = Task(
|
|
description="Generate summary of events in San Francisco from fetched data",
|
|
expected_output="A complete report on the customer and their customers and competitors, including their demographics, preferences, market positioning and audience engagement.",
|
|
agent=summary_generator_agent,
|
|
)
|
|
|
|
# Create a crew with the tasks
|
|
crew = Crew(
|
|
agents=[data_fetcher_agent, data_processor_agent, summary_generator_agent],
|
|
tasks=[task1, conditional_task, task3],
|
|
verbose=True,
|
|
planning=True
|
|
)
|
|
|
|
# Run the crew
|
|
result = crew.kickoff()
|
|
print("results", result)
|
|
``` |