Skip to content

CLDSRV-935: fix claude review#6199

Merged
bert-e merged 1 commit into
development/9.2from
bugfix/CLDSRV-935-fix-claude-review
Jun 22, 2026
Merged

CLDSRV-935: fix claude review#6199
bert-e merged 1 commit into
development/9.2from
bugfix/CLDSRV-935-fix-claude-review

Conversation

@leif-scality

@leif-scality leif-scality commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Problem

Claude code reviews silently stop on PRs targeting development/9.4. The Anthropic
review action requires .github/workflows/review.yml to be byte-identical to the
default branch
(development/9.3). 9.4's copy had drifted to 2-space indentation
(vs 9.3's 4-space) from a hand-resolved merge conflict when #6194 waterfalled in, so
validation failed and the job went green without posting a review.

Fix

Standardize review.yml on Prettier's native 2-space indentation and land it at
the root of the 9.x line (development/9.2) so it waterfalls up to 9.3 and 9.4 —
making 9.2 / 9.3 / 9.4 converge on a single, identical file.

Going to 2-space (rather than dragging 9.4 back to 4-space) means the file matches
Prettier's default style and the six other workflow files, so no .prettierignore
carve-out
is needed to keep the drift from recurring.

Notes

  • Targets development/9.2 so the change waterfalls up the whole 9.x line; the default
    branch (9.3) becomes 2-space via the waterfall, which is exactly what the review
    action validates against.
  • The resulting review.yml is byte-identical to 9.4's current copy, so the waterfall
    converges with no conflict.
  • review.yml is the only branch with the file in {9.2, 9.3, 9.4}; 9.0/9.1 don't have it.

@bert-e

bert-e commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Hello leif-scality,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval
/bypass_build_status Bypass the build and test status
/bypass_commit_size Bypass the check on the size of the changeset TBA
/bypass_incompatible_branch Bypass the check on the source branch prefix
/bypass_jira_check Bypass the Jira issue check
/bypass_peer_approval Bypass the pull request peers' approval
/bypass_leader_approval Bypass the pull request leaders' approval
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request TBA
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

@bert-e

bert-e commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Incorrect fix version

The Fix Version/s in issue CLDSRV-935 contains:

  • None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

  • 9.4.0

Please check the Fix Version/s of CLDSRV-935, or the target
branch of this pull request.

@codecov

codecov Bot commented Jun 22, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.49%. Comparing base (c17953d) to head (f30dee2).
⚠️ Report is 1 commits behind head on development/9.2.
✅ All tests successful. No failed tests found.

Additional details and impacted files

Impacted file tree graph
see 3 files with indirect coverage changes

@@                 Coverage Diff                 @@
##           development/9.2    #6199      +/-   ##
===================================================
- Coverage            84.50%   84.49%   -0.01%     
===================================================
  Files                  204      204              
  Lines                13217    13217              
===================================================
- Hits                 11169    11168       -1     
- Misses                2048     2049       +1     
Flag Coverage Δ
file-ft-tests 68.12% <ø> (ø)
kmip-ft-tests 28.41% <ø> (ø)
mongo-v0-ft-tests 69.38% <ø> (+0.02%) ⬆️
mongo-v1-ft-tests 69.35% <ø> (-0.06%) ⬇️
multiple-backend 35.68% <ø> (ø)
sur-tests 35.99% <ø> (-0.81%) ⬇️
sur-tests-inflights 37.83% <ø> (+0.03%) ⬆️
unit 70.34% <ø> (ø)
utapi-v2-tests 34.72% <ø> (+0.03%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@delthas delthas left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Could you instead reformat to 2-space (and target 9.2+)?

This will make us compliant without the need for a prettierignore

Comment thread .prettierignore Outdated
Standardize review.yml on Prettier's 2-space style across 9.2->9.4 so the Anthropic review action's "byte-identical to the default branch" check passes without a .prettierignore carve-out. Lands on 9.2 and waterfalls up so 9.2/9.3/9.4 converge on the same file.
@leif-scality leif-scality force-pushed the bugfix/CLDSRV-935-fix-claude-review branch from 9a7fc47 to f30dee2 Compare June 22, 2026 12:15
@bert-e

bert-e commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Branches have diverged

This pull request's source branch bugfix/CLDSRV-935-fix-claude-review has diverged from
development/9.4 by more than 50 commits.

To avoid any integration risks, please re-synchronize them using one of the
following solutions:

  • Merge origin/development/9.4 into bugfix/CLDSRV-935-fix-claude-review
  • Rebase bugfix/CLDSRV-935-fix-claude-review onto origin/development/9.4

Note: If you choose to rebase, you may have to ask me to rebuild
integration branches using the reset command.

@leif-scality leif-scality changed the base branch from development/9.4 to development/9.2 June 22, 2026 12:15
@bert-e

bert-e commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Incorrect fix version

The Fix Version/s in issue CLDSRV-935 contains:

  • None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

  • 9.2.42

  • 9.3.11

  • 9.4.0

Please check the Fix Version/s of CLDSRV-935, or the target
branch of this pull request.

@delthas delthas left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks!

@leif-scality

Copy link
Copy Markdown
Contributor Author

ping

@bert-e

bert-e commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

@leif-scality

Copy link
Copy Markdown
Contributor Author

/create_integration_branches

@bert-e

bert-e commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.8
  • development/9.0
  • development/9.1

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: create_integration_branches

@bert-e

bert-e commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

The following options are set: create_integration_branches

@leif-scality

Copy link
Copy Markdown
Contributor Author

/create_pull_requests

@leif-scality

Copy link
Copy Markdown
Contributor Author

@bert-e create_pull_requests

@bert-e

bert-e commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.8
  • development/9.0
  • development/9.1

Follow integration pull requests if you would like to be notified of
build statuses by email.

The following options are set: create_pull_requests, create_integration_branches

@bert-e

bert-e commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

The following options are set: create_pull_requests, create_integration_branches

@leif-scality

Copy link
Copy Markdown
Contributor Author

/approve

@bert-e

bert-e commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

  • ✔️ development/9.2

  • ✔️ development/9.3

  • ✔️ development/9.4

The following branches will NOT be impacted:

  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.8
  • development/9.0
  • development/9.1

This pull request does not target the following hotfix branch(es) so they
will be left untouched:

  • hotfix/7.70.45
  • hotfix/8.8.45
  • hotfix/9.0.7
  • hotfix/7.4.1
  • hotfix/7.10.15
  • hotfix/7.4.0
  • hotfix/7.4.5
  • hotfix/7.8.0
  • hotfix/7.4.2
  • hotfix/7.10.3
  • hotfix/7.4.3
  • hotfix/7.10.27
  • hotfix/7.10.8
  • hotfix/7.10.30
  • hotfix/7.4.7
  • hotfix/9.0.32
  • hotfix/7.4.6
  • hotfix/7.70.51
  • hotfix/9.2.24
  • hotfix/7.10.2
  • hotfix/7.10.49
  • hotfix/7.70.11
  • hotfix/7.70.21
  • hotfix/7.4.9
  • hotfix/7.10.1
  • hotfix/7.9.0
  • hotfix/7.6.0
  • hotfix/6.4.7
  • hotfix/7.2.0
  • hotfix/7.7.0
  • hotfix/7.70.73
  • hotfix/7.10.28
  • hotfix/7.4.10
  • hotfix/7.4.4
  • hotfix/7.10.0
  • hotfix/7.10.4
  • hotfix/7.4.8

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

  • Any commit you add on the source branch will trigger a new cycle after the
    current queue is merged.
  • Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve, create_pull_requests, create_integration_branches

@bert-e

bert-e commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Queue build failed

The corresponding build for the queue failed:

  • Checkout the status page.
  • Identify the failing build and review the logs.
  • If no issue is found, re-run the build.
  • If an issue is identified, checkout the steps below to remove
    the pull request from the queue for further analysis and maybe rebase/merge.
Remove the pull request from the queue
  • Add a /wait comment on this pull request.
  • Click on login on the status page.
  • Go into the manage page.
  • Find the option called Rebuild the queue and click on it.
    Bert-E will loop again on all pull requests to put the valid ones
    in the queue again, while skipping the one with the /wait comment.
  • Wait for the new queue to merge, then merge/rebase your pull request
    with the latest changes to then work on a proper fix.
  • Once the issue is fixed, delete the /wait comment and
    follow the usual process to merge the pull request.

@bert-e

bert-e commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/9.2

  • ✔️ development/9.3

  • ✔️ development/9.4

The following branches have NOT changed:

  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.8
  • development/9.0
  • development/9.1

Please check the status of the associated issue CLDSRV-935.

Goodbye leif-scality.

@bert-e bert-e merged commit f30dee2 into development/9.2 Jun 22, 2026
79 of 80 checks passed
@bert-e bert-e deleted the bugfix/CLDSRV-935-fix-claude-review branch June 22, 2026 16:39
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.

4 participants