upgrade circleici

[raffaele-oplabs]

Description

This pull request updates the .circleci/config.yml file to use a newer version of the ethereum-optimism/circleci-utils orb and simplifies the job steps by removing redundant utility commands.

Updates to .circleci/config.yml:

• Updated the utils orb version from 0.0.7 to 1.0.13 to ensure compatibility with the latest features and improvements.

Simplification of job steps:

• Removed the utils/get-github-access-token step, which is no longer necessary.
• Replaced utils/generate-issue-metrics-file and utils/create-github-issue-from-file steps with utils/create-github-issue-from-search to streamline the process of creating GitHub issues based on search queries.

Tests

Additional context

Metadata

[netlify]

✅ Deploy Preview for docs-optimism ready!

Name	Link
🔨 Latest commit	dd808e7
🔍 Latest deploy log	https://app.netlify.com/sites/docs-optimism/deploys/67b5e2668a139d0008013803
😎 Deploy Preview	https://deploy-preview-1387--docs-optimism.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates the CircleCI configuration by upgrading the circleci-utils orb from version 0.0.7 to 1.0.13. The developer-metrics job has been streamlined by removing the steps that previously obtained a GitHub access token and generated issue metrics files. In their place, the job now directly leverages the utils/create-github-issue-from-search command to create GitHub issues based on defined search queries for both closed issues and pull requests. The parameters for these commands, including search queries and issue titles, have been updated to reflect the new logic. The overall job structure remains intact with these modifications enhancing the process flow.

Sequence Diagram(s)

sequenceDiagram
    participant CI as CircleCI Job
    participant Utils as circleci-utils Orb
    participant GH as GitHub API

    CI->>Utils: Execute create-github-issue-from-search (for closed issues)
    Utils->>GH: Query closed issues and create issue
    CI->>Utils: Execute create-github-issue-from-search (for pull requests)
    Utils->>GH: Query pull requests and create issue

Loading

Possibly related PRs

• Migration GitHub to circleci #1185: Relates to modifications in the CircleCI developer-metrics job with similar updates to issue creation logic.

Suggested reviewers

• sbvegan

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between eb90aac and dd808e7.

📒 Files selected for processing (1)

• .circleci/config.yml (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Redirect rules - docs-optimism
• GitHub Check: Header rules - docs-optimism
• GitHub Check: Pages changed - docs-optimism

🔇 Additional comments (3)

.circleci/config.yml (3)

3-3: Orb Version Upgrade Updated
The orb utils is now set to version ethereum-optimism/[email protected], aligning with the latest features and improvements. Please verify the orb’s documentation for any breaking changes that might affect the existing job steps.

---

131-136: Streamlined GitHub Issue Generation for Closed Issues
The previous steps for obtaining the GitHub access token and generating issue metrics have been replaced by a single call to utils/create-github-issue-from-search. The search query for closed issues leverages the LAST_MONTH environment variable and includes appropriate filters. Ensure that the escaped quotes (i.e., -reason:\"not planned\") are correctly processed by the orb.

---

137-141: Streamlined GitHub Issue Generation for Open Pull Requests
The new step for processing pull requests uses utils/create-github-issue-from-search with a search query that captures PRs created in the last month. Confirm that the query correctly targets the intended pull requests and that the static parameters (issue title, labels, and assignees) fulfill your reporting requirements.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.