Skip to content

ci(review): review the SDK-sync App's pull requests - #106

Merged
MarketDataDev03 merged 1 commit into
mainfrom
code-review/trust-sdk-sync-app
Nov 2, 2026
Merged

MarketDataDev03 merged 1 commit into
mainfrom
code-review/trust-sdk-sync-app

Conversation

@MarketDataDev03

@MarketDataDev03 MarketDataDev03 commented Oct 30, 2026 •

Copy link
Copy Markdown
Collaborator

Lets the code review bot review pull requests opened by the SDK-sync pipeline's GitHub App (marketdata-sdk-sync[bot]), as sdk-py and sdk-java already do. An App is not a member of the organization, so the policy trusts it by name. Without this, the pipeline's pull requests here get no code review and are handed to a person.

What changes

One line in .github/code-review/policy.yml, with a comment: trusted_authors: ["marketdata-sdk-sync[bot]"]. Nothing else: backends, gate, require_ci_green, ignore_paths and the review rules stay as they are.

Proof

The same line works in the other SDKs. sdk-java and sdk-py carry this exact line, and the bot reviews the pull requests the App opens there. Each of these is authored by app/marketdata-sdk-sync, and each has a Code review check run that started and completed:

The file parses, with the value in place:

$ python3 -c "import yaml; d = yaml.safe_load(open('.github/code-review/policy.yml')); print(d['trusted_authors'])"
['marketdata-sdk-sync[bot]']

A pull request here from the App is not possible until this merges, because the App's pull requests are not reviewed before then. The first pipeline pull request in this repository is the check here.

@codecov

codecov Bot commented Oct 30, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.78%. Comparing base (8ed1cfd) to head (e67d234).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #106   +/-   ##
=========================================
  Coverage     99.78%   99.78%           
  Complexity      971      971           
=========================================
  Files            50       50           
  Lines          2829     2829           
=========================================
  Hits           2823     2823           
  Misses            6        6           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@marketdata-code-review

marketdata-code-review Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

✅ Ready — Code review

Version impact: none; no public SDK symbols are touched, so no release or changelog entry is required. The change trusts the SDK-sync GitHub App as a review author, and the supplied parser output plus successful sibling-SDK check runs support the configuration.

Rating patch 6/6 (exemplary) · proof 5/6 (reproducible) · overall 5/6


Reviewed e67d234 · revision 1 · codex (gpt-5.6-sol) · claude unavailable · rules: default, sdk

@MarketDataDev03

Copy link
Copy Markdown
Collaborator Author

@marketdata-code-review re-review

@MarketDataDev02 MarketDataDev02 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same line as sdk-py and sdk-java: the policy parses with the bot's own loader into a single trusted_authors entry, marketdata-sdk-sync[bot], which is the exact login on the App's PRs, and ignore_authors does not exclude it. The trust check only adds listed logins on top of org membership, the caller workflow has no author filter, and auto_approve and auto_merge stay off, so the App gets a review and a check and nothing more.

@MarketDataDev03
MarketDataDev03 merged commit 5db046b into main Nov 2, 2026
25 checks passed
@MarketDataDev03
MarketDataDev03 deleted the code-review/trust-sdk-sync-app branch November 2, 2026 13:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants