chore(ci): correct github-script API calls

[dnwe]

User description

Description

Since V5 of github-script the Octokit context available via github no longer has REST methods directly on it, they were moved to github.rest.* instead. Update the references in delete-comments.yml job to match.

Motivation and Context

The GitHub Actions workflow will fail when it attempts to delete a comment without this change.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have read the contributing document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

---

PR Type

Bug fix, Enhancement

---

Description

• Updated the GitHub Actions workflow to use the new github.rest.* syntax for API calls, ensuring compatibility with version 5 of github-script.
• Modified the deleteComment and block methods to align with the updated Octokit context, preventing workflow failures.

---

Changes walkthrough 📝

	Relevant files
Bug fix	delete-comments.yml Update GitHub API calls to new Octokit syntax                        .github/workflows/delete-comments.yml Updated GitHub API calls to use github.rest.* syntax. Changed deleteComment and block methods to use the new Octokit context. +2/-2

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[CLAassistant]

All committers have signed the CLA.

[qodo-merge-pro]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[qodo-merge-pro]

PR Code Suggestions ✨

Category	Suggestion	Score
Possible issue	Remove unnecessary parameter from API call to prevent potential errors Remove the repo parameter from the github.rest.users.block() call as it's not required for this API endpoint and may cause an error. .github/workflows/delete-comments.yml [41-45] await github.rest.users.block({ owner: context.repo.owner, - repo: context.repo.repo, user_id: userId }); Apply this suggestion Suggestion importance[1-10]: 9 Why: Removing the repo parameter from the github.rest.users.block() call is crucial as it is not required and could cause errors, thus improving the robustness of the code.	9
Best practice	✅ Use the preferred parameter for user identification in the block operation Suggestion Impact: The commit changed the parameter from user_id to username in the block operation, aligning with the suggestion to use the preferred parameter for user identification. code diff: - const userId = context.payload.comment.user.id; - await github.rest.users.block({ - owner: context.repo.owner, - repo: context.repo.repo, - user_id: userId + const username = context.payload.comment.user.login + await github.rest.orgs.blockUser({ + org: context.repo.owner, + username: username Consider using the username parameter instead of user_id when blocking a user. The GitHub API prefers username for user identification in the block operation. .github/workflows/delete-comments.yml [41-45] await github.rest.users.block({ owner: context.repo.owner, - repo: context.repo.repo, - user_id: userId + username: context.payload.comment.user.login }); Apply this suggestion Suggestion importance[1-10]: 8 Why: The suggestion to use username instead of user_id aligns with GitHub API best practices for user identification, which can improve code reliability and maintainability.	8

[diemol]

Thank you, @dnwe!