[ambushwork]

What does this PR do?

notify:dogfood-app now requests its token for ddoghq/datadog-android. ci/scripts/dogfood.py now has a GitHub owner and repo for each target:

• app → ddoghq/datadog-android
• demo → DataDog/shopist-android
• gradle-plugin → DataDog/dd-sdk-android-gradle-plugin

Motivation

DataDog/datadog-android now returns 404, so the dogfood app job can't get a token or open its PR.

Additional Notes

• The SDK diff link in the PR body the script generates still points to DataDog/dd-sdk-android.
• The token policy in ddoghq/datadog-android is unchanged.
• py_compile passes and the pipeline YAML parses.
• The job only runs on tags, so it hasn't been run end to end.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Make sure you discussed the feature or bugfix with the maintaining team in an Issue
• Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

[datadog-datadog-prod-us1-2]

 

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 72.07% (+0.02%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 4726e6d | Docs | View more details | Give us feedback!}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-29T17:07:07.090730Z	4726e6d	Draft marked ready
🔒 Security Review	✅ Completed 2026-10-29T17:09:11.586010Z	4726e6d	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[datadog-datadog-prod-us1-2]

More details

The app target consistently uses ddoghq/datadog-android for token acquisition, cloning, signed pushes, and PR creation, while the other targets retain their existing owners. Live token issuance and tag-triggered CI execution remain unverified.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 4726e6d}