fix(ci): add concurrency group

[MaxMustermann2]

Prevent the same job from running on multiple commit hashes by cancelling any previous jobs that are running.

Summary by CodeRabbit

• Workflow Improvements
  • Enhanced GitHub Actions workflows by adding concurrency management.
  • Workflows now automatically cancel in-progress runs when a new workflow is triggered.
  • Improved control flow to prevent status updates when the parent workflow is cancelled.
  • Streamlined handling of workflow outcomes for better efficiency across multiple CI processes.

[coderabbitai]

Walkthrough

The pull request introduces concurrency configurations to four GitHub Actions workflow files: forge-ci.yml, lint.yml, slither.yml, and compare-layouts.yml. These changes implement a consistent approach to managing workflow executions by adding a concurrency block that cancels in-progress workflows when a new workflow is triggered. Additionally, the handling of workflow run conclusions is refined to prevent updates when parent workflows are cancelled, ensuring efficient resource management and preventing redundant workflow runs.

Changes

File	Change Summary
.github/workflows/forge-ci.yml	Added concurrency configuration with group based on workflow name and PR/ref/SHA
.github/workflows/lint.yml	Added concurrency configuration with group based on workflow name and PR/ref/SHA
.github/workflows/slither.yml	Added concurrency configuration with group based on workflow name and PR/ref/SHA
.github/workflows/compare-layouts.yml	Updated job conditions to prevent actions when parent workflow is cancelled; modified commit status handling
.github/workflows/status-comment.yml	Updated conditional checks to skip actions if parent workflow is cancelled

Possibly related PRs

• feat(ci): carve out storage layout CI #127: The changes in this PR enhance the CI process related to storage layout comparisons, which is directly relevant to the concurrency management introduced in the main PR's workflow.
• fix(ci): use PR addrs to compare layouts #139: This PR addresses issues in the compare-layouts.yml workflow, ensuring that the most current deployment addresses are used for layout comparisons, which relates to the concurrency and management of workflows in the main PR.

Suggested reviewers

• magj2006
• adu-web3
• bwhour

Poem

🐰 Workflows dance, no more delay
Concurrency cancels the old way
PR triggers, jobs align
Efficiency now intertwines
Rabbit's magic, workflows bright! 🚀

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f301df4 and f32d207.

📒 Files selected for processing (2)

• .github/workflows/compare-layouts.yml (9 hunks)
• .github/workflows/status-comment.yml (3 hunks)

🔇 Additional comments (10)

.github/workflows/status-comment.yml (3)

38-39: LGTM! Well-documented condition for workflow efficiency.

The condition correctly skips processing for cancelled workflows while ensuring failures are still captured in comments.

---

60-60: LGTM! Consistent condition handling.

The condition maintains consistency with the PR number step, preventing unnecessary message construction for cancelled workflows.

---

80-80: LGTM! Completes the workflow cancellation handling.

The condition consistently prevents comment operations for cancelled workflows, completing the chain of cancellation handling.

.github/workflows/compare-layouts.yml (7)

34-37: LGTM! Clear documentation of workflow cancellation logic.

The condition and its documentation clearly explain how cancelled workflows are handled, preventing unnecessary status updates while ensuring failures are still recorded.

---

99-99: LGTM! Smart approach to reduce notification noise.

Using skip-install parameter instead of an if condition is an elegant way to avoid job skipped emails.

---

107-109: LGTM! Critical optimization for workflow reliability.

Using if: always() for matrix generation is crucial as it prevents unnecessary cascading failures when the matrix is empty.

---

147-147: LGTM! Clear and consistent condition.

The explicit success check aligns with the workflow's cancellation handling strategy.

---

253-254: LGTM! Well-documented status update logic.

The condition maintains consistency with the workflow's cancellation handling while ensuring failures are properly reported.

---

279-279: LGTM! Consistent message handling.

The condition maintains consistency with the workflow's cancellation handling strategy.

---

295-295: LGTM! Consistent comment handling.

The condition maintains consistency with the workflow's cancellation handling strategy.

---

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 or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[github-actions]

✅ The Forge CI workflow has completed successfully. Check the workflow run for details. (f32d207)

[github-actions]

✅ The Solhint workflow has completed successfully. Check the workflow run for details. (f32d207)

[github-actions]

✅ The Slither Analysis workflow has completed successfully. Check the workflow run for details. (f32d207)

[github-actions]

✅ The Compare Storage Layouts workflow has completed successfully. Check the workflow run for details. (f32d207)

[adu-web3]

good to have to save resources

[bwhour]

looks good.