chore(deps): bump marocchino/sticky-pull-request-comment from 1.1.0 to 2.9.0

[dependabot]

Bumps marocchino/sticky-pull-request-comment from 1.1.0 to 2.9.0.

Release notes

Sourced from marocchino/sticky-pull-request-comment's releases.

v2.9.0

• Update deps
• Use node 20

v2.8.0

• Add skip_unchanged input
• Update deps

v2.7.0

Update deps. Add two output.

• previous_comment_id: "ID of previous comment, if found"
• created_comment_id: "ID of newly created comment, if any"

v2.6.2

Reverted changes in version 2.6. As a result, the base_url has been removed.

v2.6.1

Change base_url default to ${{ env.GITHUB_API_URL }}

v2.6.0

• Update deps
• Add base_url option. (default: 'https://api.github.com')

v2.5.0

• Update deps
• Add only_update option.
• Add owner option.

v2.4.0

• Update deps
• Add only_create option.

v2.3.1

• Update deps
• Change ignore empty default from true to false (This change will fix bug delete or hide comment not works)

v2.3.0

• Support glob path
• Add follow_symbolic_links for path
• Add ignore_empty for skip empty body
• Update README for new output syntax

Update deps

• Use node 16
• Update npm deps

v2.2.0

Add hide, hide_details, hide_and_recreate, hide_classsify options

... (truncated)

Commits

• 331f8f5 📦️ build
• 5c844f7 ⬆️ node 20
• 989f9fa Merge pull request #1236 from marocchino/dependabot/npm_and_yarn/typescript-e...
• 42b601d build(deps-dev): Bump @​typescript-eslint/parser from 6.19.0 to 6.20.0
• 627a535 Merge pull request #1227 from marocchino/dependabot/npm_and_yarn/ts-jest-29.1.2
• 85fbd23 Merge pull request #1239 from marocchino/dependabot/npm_and_yarn/types/node-2...
• 9ecb719 Merge pull request #1240 from marocchino/dependabot/npm_and_yarn/octokit/grap...
• 76f17ea Merge pull request #1238 from MauriceArikoglu/patch-1
• b11ff05 build(deps): Bump @​octokit/graphql-schema from 14.47.1 to 14.52.0
• e141788 build(deps-dev): Bump @​types/node from 20.11.5 to 20.11.14
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Summary by CodeRabbit

• Chores
  • Updated the version of the sticky pull request comment action to improve linting feedback.
  • Corrected indentation in the workflow configuration for better readability.
  • Specified multiple Python versions for testing to enhance compatibility.
  • Updated the checkout action version for improved performance in linting and documentation jobs.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (878af61) 83.99% compared to head (0da4492) 83.99%.
Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #108   +/-   ##
=======================================
  Coverage   83.99%   83.99%           
=======================================
  Files          21       21           
  Lines        1506     1506           
=======================================
  Hits         1265     1265           
  Misses        241      241           

[holtgrewe]

@coderabbitai full review

[coderabbitai]

✅ Actions performed

Full review triggered.

[coderabbitai]

Walkthrough

The changes in the GitHub Actions workflow configuration involve updating action versions, correcting indentation, and specifying Python version matrices. The marocchino/sticky-pull-request-comment action was updated from version v1.1.0 to v2.9.0, and the actions/checkout action was updated from v2 to v4 in the linting and sphinx-docs jobs. The structure of the jobs remains the same, with dependencies intact, and the testing job continues to run across multiple Python versions.

Changes

File	Change Summary
.github/workflows/main.yml	- Updated marocchino/sticky-pull-request-comment from v1.1.0 to v2.9.0 in linting job. - Corrected indentation of Comment PR step in linting job. - Updated actions/checkout from v2 to v4 in linting and sphinx-docs jobs. - Maintained actions/checkout as v2 in testing job. - Specified Python versions in testing job as 3.10, 3.11, and 3.12.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GitHub Actions
    participant Linting Job
    participant Testing Job

    User->>GitHub Actions: Create Pull Request
    GitHub Actions->>Linting Job: Run Linting
    Linting Job->>GitHub Actions: Comment on PR if linting fails
    Linting Job->>Testing Job: Trigger Testing
    Testing Job->>GitHub Actions: Run Tests across Python versions

Loading

🐰 "In the garden where code does bloom,
A pull request brings joy, not gloom.
With actions updated, we hop with glee,
Linting and testing, as smooth as can be!
So let’s celebrate with a dance and a cheer,
For every change, we hold dear!" 🐇

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 878af61 and 0da4492.

📒 Files selected for processing (1)

• .github/workflows/main.yml (1 hunks)

🧰 Additional context used

🔇 Additional comments (2)

.github/workflows/main.yml (2)

Line range hint 42-46: No additional changes required.

After verifying the usage of the marocchino/sticky-pull-request-comment action, it appears that our current implementation doesn't require any additional changes. The update from v1.1.0 to v2.9.0 should be backwards compatible for our use case, as we're only using the basic 'message' and 'GITHUB_TOKEN' inputs which haven't changed.

---

42-42: Dependency update looks good.

The update of marocchino/sticky-pull-request-comment action from v1.1.0 to v2.9.0 matches the PR description. This change is part of the dependency bump initiated by Dependabot.

Let's verify if there are any breaking changes or new features that might require additional updates:

✅ Verification successful

Dependency update verified successfully.

No breaking changes or new features detected for marocchino/sticky-pull-request-comment@v2.9.0. The workflow update is consistent and requires no further changes.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any usage of new features or breaking changes in v2.9.0

# Test: Search for any usage of new input options introduced in v2.9.0
rg --type yaml 'marocchino/sticky-pull-request-comment@v2' -A 10 .github/workflows/main.yml

Length of output: 438

---

🪧 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 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.

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.