Document Bits Code conflict handling

[EricCeres]

What does this PR do? What is the motivation?

Documents that Bits Code monitors pull or merge request state, in addition to CI logs, to fix failures and merge blockers.

Source PR: https://github.com/DataDog/code-gen-backend/pull/13567

Changes

• Updated hugo/content/en/bits_ai/bits_code/_index.md to describe PR and MR collaboration in terms of fixing failures and merge blockers.
• Preserved the existing statement that Bits Code never auto-merges pull or merge requests.

Testing

• Ran git diff --check.
• Attempted to run vale hugo/content/en/bits_ai/bits_code/_index.md, but Vale is not installed in this environment.
• Attempted to run python -m vale --version, but the Vale module is not installed.

Merge readiness

• Ready for merge

For Datadog employees:

• ⚠️ Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR.
• 🤖 New: Comment with /review to run an automated check that catches common issues before a Documentation team member reviews your PR.

AI assistance

Used Bits Code powered by Codex CLI to edit documentation and prepare PR metadata.

Additional notes

None.

---

PR by Bits - View session in Datadog

Comment @DataDog to request changes

[datadog-prod-us1-3]

View session in Datadog

Bits Code status: ✅ Done

CI Auto-fix: Disabled | Enable

Comment @DataDog to request changes

[datadog-prod-us1-6]

I can only run on private repositories.

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/dd/eric.ceres/bits-code-conflict-handling/bits_ai/bits_code/

[jeff-morgan-dd]

Looks good, thank you for the PR!