Skip to content

[fix](ci) Use only valid Codex review auth - #66158

Closed
shuke987 wants to merge 1 commit into
apache:masterfrom
shuke987:codex/only-use-auth-json-4
Closed

[fix](ci) Use only valid Codex review auth#66158
shuke987 wants to merge 1 commit into
apache:masterfrom
shuke987:codex/only-use-auth-json-4

Conversation

@shuke987

Copy link
Copy Markdown
Contributor

What problem does this PR solve?

Issue Number: None

Related PR: None

Problem Summary: The automated code review runner randomly selected auth.json.2, auth.json.3, or auth.json.4. The first two credentials now have revoked refresh tokens and cause reviews to fail with HTTP 401. This change temporarily restricts review runs to the currently valid auth.json.4 credential.

Release note

None

Check List (For Author)

  • Test: Manual test
    • Parsed .github/workflows/code-review-runner.yml as YAML
    • Ran git diff --check
  • Behavior changed: Yes. Automated code reviews temporarily use only auth.json.4.
  • Does this need documentation: No

### What problem does this PR solve?

Issue Number: None

Related PR: None

Problem Summary: The automated code review runner randomly selected auth.json.2, auth.json.3, or auth.json.4. The first two credentials now have revoked refresh tokens and cause reviews to fail with HTTP 401. Restrict review runs to the currently valid auth.json.4 credential.

### Release note

None

### Check List (For Author)

- Test: Manual test
    - Parsed code-review-runner.yml as YAML
    - Ran git diff --check
- Behavior changed: Yes. Automated code reviews temporarily use only auth.json.4.
- Does this need documentation: No
@hello-stephen

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@shuke987 shuke987 closed this Jul 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants