Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update algorithms.md with PageRank #116

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Update algorithms.md with PageRank #116

wants to merge 5 commits into from

Conversation

gkorland
Copy link
Contributor

@gkorland gkorland commented Jan 16, 2025

PR Type

Documentation


Description

  • Added documentation for the PageRank algorithm in cypher/algorithms.md.

  • Included usage examples and parameter details for PageRank.

  • Provided notes on PageRank assumptions and additional references.


Changes walkthrough 📝

Relevant files
Documentation
algorithms.md
Documented PageRank algorithm usage and details                   

cypher/algorithms.md

  • Added a new section for the PageRank algorithm.
  • Included usage syntax and example for algo.pageRank.
  • Detailed parameters, outputs, and assumptions for PageRank.
  • Provided a reference to Wikipedia for further reading.
  • +50/-0   

    Need help?
  • Type /help how to ... in the comments thread for any question about Qodo Merge usage.
  • Check out the documentation for more information.
  • Summary by CodeRabbit

    • Documentation
      • Enhanced documentation for Breadth-First Search (BFS) algorithm with clear usage statements and parameter descriptions.
      • Added new section for PageRank algorithm, including purpose, parameters, expected outputs, and usage examples.
      • Defined new parameters and outputs for PageRank, clarifying their roles in the computation.

    @gkorland gkorland requested review from swilly22 and Copilot January 16, 2025 10:27
    Copy link
    Contributor

    coderabbitai bot commented Jan 16, 2025

    Warning

    Rate limit exceeded

    @gkorland has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 15 minutes and 29 seconds before requesting another review.

    ⌛ How to resolve this issue?

    After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

    We recommend that you space out your commits to avoid hitting the rate limit.

    🚦 How do rate limits work?

    CodeRabbit enforces hourly rate limits for each developer per organization.

    Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

    Please see our FAQ for further information.

    📥 Commits

    Reviewing files that changed from the base of the PR and between 44bdb20 and b264509.

    📒 Files selected for processing (1)
    • cypher/algorithms.md (2 hunks)

    Walkthrough

    The pull request introduces significant enhancements to the documentation of two graph algorithms, Breadth-First Search (BFS) and PageRank, in the cypher/algorithms.md file. It includes detailed descriptions of the usage, parameters, and outputs for both algorithms, providing clear guidance for developers on how to implement these techniques effectively.

    Changes

    File Change Summary
    cypher/algorithms.md Enhanced BFS section with usage details and parameter descriptions; added new PageRank section with usage, parameters, and outputs.

    Poem

    🐰 In the realm of graphs, we leap and bound,
    With BFS and PageRank, new wonders abound!
    Parameters and outputs, all neatly defined,
    A rabbit's delight in the code we unwind.
    Hop on, dear friends, let algorithms play,
    In the dance of data, we find our way! 🔍


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

    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.

    Copy link

    Qodo Merge was enabled for this repository. To continue using it, please link your Git account with your Qodo account here.

    PR Reviewer Guide 🔍

    Here are some key observations to aid the review process:

    ⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
    🧪 No relevant tests
    🔒 No security concerns identified
    ⚡ Recommended focus areas for review

    Broken Link

    The Wikipedia links appear as plain text rather than proper markdown links, which makes them non-functional. The word 'Wikipedia' appears twice without proper linking.

    Wikipedia
    
    Usage:
    

    CALL algo.pageRank(
    'NodeLabel', // The label of the nodes to include in the computation
    'RELATIONSHIP_TYPE' // The type of relationships to consider
    )
    YIELD nodeId, score

    
    Parameters:
    
        'NodeLabel': The label of the nodes to include in the computation.
        'RELATIONSHIP_TYPE': The type of relationships to consider. Only edges of this type will be used in the PageRank calculation.
    
    YIELD:
    
        nodeId: The internal ID of the node.
        score: The PageRank score assigned to the node.
    
    Example:
    
    

    CALL algo.pageRank('Page', 'LINKS_TO')
    YIELD nodeId, score
    RETURN nodeId, score
    ORDER BY score DESC

    
    In this example, the algo.pageRank function computes the PageRank scores for all nodes labeled 'Page', considering only 'LINKS_TO' relationships. The results are returned with nodes ordered by their PageRank score in descending order.
    
    Note:
    
        Ensure that the graph contains nodes with the specified label and relationships of the specified type; otherwise, the function may return an empty result set.
        The PageRank algorithm assumes that the graph is directed; thus, the direction of relationships is taken into account during computation.
        The damping factor, which represents the probability of continuing from one node to another, is typically set to 0.85. This value can influence the distribution of PageRank scores.
        Wikipedia
    
    Missing Parameters

    The documentation mentions a damping factor parameter but does not explain how to configure it in the function call. Other potential parameters like max iterations or convergence tolerance are also not documented.

    CALL algo.pageRank(
    'NodeLabel', // The label of the nodes to include in the computation
    'RELATIONSHIP_TYPE' // The type of relationships to consider
    )
    YIELD nodeId, score

    
    </details>
    
    </td></tr>
    </table>
    

    Copy link
    Contributor

    @Copilot Copilot AI left a comment

    Choose a reason for hiding this comment

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

    Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

    Comments suppressed due to low confidence (2)

    cypher/algorithms.md:72

    • The word 'Wikipedia' seems out of place and should be removed.
    Wikipedia
    

    cypher/algorithms.md:29

    • The term 'Page Rank' should be consistently used as 'PageRank' to match the rest of the document.
    ## Page Rank
    

    cypher/algorithms.md Outdated Show resolved Hide resolved
    Copy link

    qodo-merge-pro bot commented Jan 16, 2025

    Qodo Merge was enabled for this repository. To continue using it, please link your Git account with your Qodo account here.

    PR Code Suggestions ✨

    Explore these optional code suggestions:

    CategorySuggestion                                                                                                                                    Score
    General
    Improve documentation clarity by properly formatting external references using Markdown link syntax

    Remove the standalone "Wikipedia" text that appears twice in the document, and
    instead properly integrate the Wikipedia reference into the text using proper
    Markdown link syntax.

    cypher/algorithms.md [33-34]

    -The function executes the PageRank algorithm on nodes of a specified label, considering only edges of a given relationship type. PageRank is an algorithm originally developed by Google to rank web pages by measuring their relative importance within a linked network. It assigns a numerical weight to each node, indicating its significance based on the structure of incoming links.
    -Wikipedia
    +The function executes the PageRank algorithm on nodes of a specified label, considering only edges of a given relationship type. PageRank is an algorithm originally developed by Google to rank web pages by measuring their relative importance within a linked network. It assigns a numerical weight to each node, indicating its significance based on the structure of incoming links. For more details, see [Wikipedia's PageRank article](https://en.wikipedia.org/wiki/PageRank).
    • Apply this suggestion
    Suggestion importance[1-10]: 7

    Why: The suggestion improves documentation readability by properly integrating Wikipedia references into the text using Markdown links, replacing standalone "Wikipedia" mentions that appear abruptly in the text.

    7
    ✅ Enable syntax highlighting in code blocks by specifying the language identifier
    Suggestion Impact:The commit added 'cypher' language identifier to two code blocks in the documentation

    code diff:

    -```
    +```cypher
     CALL algo.pageRank(
       'NodeLabel',        // The label of the nodes to include in the computation
       'RELATIONSHIP_TYPE' // The type of relationships to consider
    @@ -55,7 +59,7 @@
     
     Example:
     
    -```
    +```cypher
     CALL algo.pageRank('Page', 'LINKS_TO')
     YIELD nodeId, score

    Add code block language identifiers to the Cypher query examples for proper syntax
    highlighting.

    cypher/algorithms.md [38-44]

    -```
    +```cypher
     CALL algo.pageRank(
       'NodeLabel',        // The label of the nodes to include in the computation
       'RELATIONSHIP_TYPE' // The type of relationships to consider
     )
     YIELD nodeId, score
    
    - [ ] **Apply this suggestion** <!-- /improve --apply_suggestion=1 -->
    
    <details><summary>Suggestion importance[1-10]: 5</summary>
    
    Why: Adding the 'cypher' language identifier to code blocks will enable proper syntax highlighting, making the examples more readable and easier to understand, though it's a relatively minor enhancement.
    
    </details></details></td><td align=center>5
    
    </td></tr></tr></tbody></table>
    
    

    Copy link
    Contributor

    @coderabbitai coderabbitai bot left a comment

    Choose a reason for hiding this comment

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

    Actionable comments posted: 0

    🧹 Nitpick comments (4)
    cypher/algorithms.md (4)

    34-35: Improve Wikipedia reference formatting.

    The word "Wikipedia" appears to be a misplaced reference. Consider formatting it as a proper citation or removing it if unnecessary.

    -Wikipedia
    +For more information, see [Wikipedia's article on PageRank](https://en.wikipedia.org/wiki/PageRank).

    38-50: Fix Markdown formatting issues.

    The code blocks need proper formatting:

    1. Specify the language for fenced code blocks
    2. Use fenced code blocks consistently instead of indentation
    -```
    +```cypher
     CALL algo.pageRank(
       'NodeLabel',        // The label of the nodes to include in the computation
       'RELATIONSHIP_TYPE' // The type of relationships to consider
     )
     YIELD nodeId, score
    • 'NodeLabel': The label of the nodes to include in the computation.
    • 'RELATIONSHIP_TYPE': The type of relationships to consider. Only edges of this type will be used in the PageRank calculation.
      + +'NodeLabel': The label of the nodes to include in the computation. +'RELATIONSHIP_TYPE': The type of relationships to consider. Only edges of this type will be used in the PageRank calculation. +
    
    <details>
    <summary>🧰 Tools</summary>
    
    <details>
    <summary>🪛 Markdownlint (0.37.0)</summary>
    
    38-38: null
    Fenced code blocks should have a language specified
    
    (MD040, fenced-code-language)
    
    ---
    
    48-48: Expected: fenced; Actual: indented
    Code block style
    
    (MD046, code-block-style)
    
    </details>
    
    </details>
    
    ---
    
    `58-63`: **Add language specification to code block.**
    
    Specify the language for the example code block.
    
    ```diff
    -```
    +```cypher
     CALL algo.pageRank('Page', 'LINKS_TO')
     YIELD nodeId, score
     RETURN nodeId, score
     ORDER BY score DESC
    
    
    <details>
    <summary>🧰 Tools</summary>
    
    <details>
    <summary>🪛 Markdownlint (0.37.0)</summary>
    
    58-58: null
    Fenced code blocks should have a language specified
    
    (MD040, fenced-code-language)
    
    </details>
    
    </details>
    
    ---
    
    `69-74`: **Clean up notes section and references.**
    
    The notes section needs consistent formatting, and the Wikipedia references are redundant.
    
    ```diff
    -    Ensure that the graph contains nodes with the specified label and relationships of the specified type; otherwise, the function may return an empty result set.
    -    The PageRank algorithm assumes that the graph is directed; thus, the direction of relationships is taken into account during computation.
    -    The damping factor, which represents the probability of continuing from one node to another, is typically set to 0.85. This value can influence the distribution of PageRank scores.
    -    Wikipedia
    -
    -For more detailed information on the PageRank algorithm, refer to the Wikipedia article on PageRank.
    +```
    +- Ensure that the graph contains nodes with the specified label and relationships of the specified type; otherwise, the function may return an empty result set.
    +- The PageRank algorithm assumes that the graph is directed; thus, the direction of relationships is taken into account during computation.
    +- The damping factor, which represents the probability of continuing from one node to another, is typically set to 0.85. This value can influence the distribution of PageRank scores.
    +```
    +
    +For more information, see [Wikipedia's article on PageRank](https://en.wikipedia.org/wiki/PageRank).
    
    🧰 Tools
    🪛 Markdownlint (0.37.0)

    69-69: Expected: fenced; Actual: indented
    Code block style

    (MD046, code-block-style)

    📜 Review details

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

    📥 Commits

    Reviewing files that changed from the base of the PR and between f571c15 and ea6ea15.

    📒 Files selected for processing (1)
    • cypher/algorithms.md (2 hunks)
    🧰 Additional context used
    🪛 Markdownlint (0.37.0)
    cypher/algorithms.md

    38-38: null
    Fenced code blocks should have a language specified

    (MD040, fenced-code-language)


    58-58: null
    Fenced code blocks should have a language specified

    (MD040, fenced-code-language)


    48-48: Expected: fenced; Actual: indented
    Code block style

    (MD046, code-block-style)


    53-53: Expected: fenced; Actual: indented
    Code block style

    (MD046, code-block-style)


    69-69: Expected: fenced; Actual: indented
    Code block style

    (MD046, code-block-style)

    🔇 Additional comments (2)
    cypher/algorithms.md (2)

    Line range hint 13-28: LGTM! Clear and comprehensive BFS documentation.

    The BFS section is well-structured with clear explanations of parameters and outputs.


    29-75: Well-documented PageRank implementation!

    The PageRank documentation is comprehensive and technically accurate, covering all essential aspects including usage, parameters, outputs, and important considerations. The examples and explanations are clear and helpful.

    🧰 Tools
    🪛 Markdownlint (0.37.0)

    38-38: null
    Fenced code blocks should have a language specified

    (MD040, fenced-code-language)


    58-58: null
    Fenced code blocks should have a language specified

    (MD040, fenced-code-language)


    48-48: Expected: fenced; Actual: indented
    Code block style

    (MD046, code-block-style)


    53-53: Expected: fenced; Actual: indented
    Code block style

    (MD046, code-block-style)


    69-69: Expected: fenced; Actual: indented
    Code block style

    (MD046, code-block-style)

    Copy link
    Contributor

    @coderabbitai coderabbitai bot left a comment

    Choose a reason for hiding this comment

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

    Actionable comments posted: 0

    🧹 Nitpick comments (5)
    cypher/algorithms.md (5)

    Line range hint 13-28: Consider adding a code example for BFS.

    The BFS documentation would benefit from a practical example, similar to the one provided in the PageRank section. This would help users understand how to use the algorithm in practice.

    Would you like me to provide a sample code example for the BFS usage?


    42-54: Fix markdown formatting issues.

    Please address the following markdown formatting issues:

    1. Add language specification to the code fence (e.g., ```cypher)
    2. Use consistent code block style for parameters (prefer fenced over indented)
    -```
    +```cypher
     CALL algo.pageRank(
       'NodeLabel',        // The label of the nodes to include in the computation
       'RELATIONSHIP_TYPE' // The type of relationships to consider
     )
     YIELD nodeId, score
    • 'NodeLabel': The label of the nodes to include in the computation.
    • 'RELATIONSHIP_TYPE': The type of relationships to consider. Only edges of this type will be used in the PageRank calculation.
      +text +'NodeLabel': The label of the nodes to include in the computation. +'RELATIONSHIP_TYPE': The type of relationships to consider. Only edges of this type will be used in the PageRank calculation. +
    
    <details>
    <summary>🧰 Tools</summary>
    
    <details>
    <summary>🪛 Markdownlint (0.37.0)</summary>
    
    42-42: null
    Fenced code blocks should have a language specified
    
    (MD040, fenced-code-language)
    
    ---
    
    52-52: Expected: fenced; Actual: indented
    Code block style
    
    (MD046, code-block-style)
    
    </details>
    
    </details>
    
    ---
    
    `57-59`: **Use consistent code block style for yield values.**
    
    Convert the indented code block to a fenced code block for consistency.
    
    ```diff
    -    nodeId: The internal ID of the node.
    -    score: The PageRank score assigned to the node.
    +```text
    +nodeId: The internal ID of the node.
    +score: The PageRank score assigned to the node.
    +```
    
    🧰 Tools
    🪛 Markdownlint (0.37.0)

    57-57: Expected: fenced; Actual: indented
    Code block style

    (MD046, code-block-style)


    62-67: Add language specification and enhance the example.

    1. Add language specification to the code fence
    2. Consider adding sample output to make the example more complete
    -```
    +```cypher
     CALL algo.pageRank('Page', 'LINKS_TO')
     YIELD nodeId, score
     RETURN nodeId, score
     ORDER BY score DESC

    +Example output:
    +text +╒════════╤═══════╕ +│ nodeId │ score │ +╞════════╪═══════╡ +│ 1 │ 0.85 │ +│ 2 │ 0.34 │ +│ 3 │ 0.21 │ +└────────┴───────┘ +

    
    <details>
    <summary>🧰 Tools</summary>
    
    <details>
    <summary>🪛 Markdownlint (0.37.0)</summary>
    
    62-62: null
    Fenced code blocks should have a language specified
    
    (MD040, fenced-code-language)
    
    </details>
    
    </details>
    
    ---
    
    `73-75`: **Use consistent code block style for notes.**
    
    Convert the indented notes to a fenced code block for consistency.
    
    ```diff
    -    Ensure that the graph contains nodes with the specified label and relationships of the specified type; otherwise, the function may return an empty result set.
    -    The PageRank algorithm assumes that the graph is directed; thus, the direction of relationships is taken into account during computation.
    -    The damping factor, which represents the probability of continuing from one node to another, is typically set to 0.85. This value can influence the distribution of PageRank scores.
    +```text
    +- Ensure that the graph contains nodes with the specified label and relationships of the specified type; otherwise, the function may return an empty result set.
    +- The PageRank algorithm assumes that the graph is directed; thus, the direction of relationships is taken into account during computation.
    +- The damping factor, which represents the probability of continuing from one node to another, is typically set to 0.85. This value can influence the distribution of PageRank scores.
    +```
    
    🧰 Tools
    🪛 Markdownlint (0.37.0)

    73-73: Expected: fenced; Actual: indented
    Code block style

    (MD046, code-block-style)

    📜 Review details

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

    📥 Commits

    Reviewing files that changed from the base of the PR and between ea6ea15 and 44bdb20.

    📒 Files selected for processing (1)
    • cypher/algorithms.md (2 hunks)
    🧰 Additional context used
    🪛 Markdownlint (0.37.0)
    cypher/algorithms.md

    42-42: null
    Fenced code blocks should have a language specified

    (MD040, fenced-code-language)


    62-62: null
    Fenced code blocks should have a language specified

    (MD040, fenced-code-language)


    52-52: Expected: fenced; Actual: indented
    Code block style

    (MD046, code-block-style)


    57-57: Expected: fenced; Actual: indented
    Code block style

    (MD046, code-block-style)


    73-73: Expected: fenced; Actual: indented
    Code block style

    (MD046, code-block-style)

    🔇 Additional comments (2)
    cypher/algorithms.md (2)

    29-39: Well-written introduction!

    The PageRank introduction provides a clear and informative explanation of the algorithm's purpose and background.


    76-78: Improve Wikipedia reference.

    The standalone "Wikipedia" text and the reference line could be improved.

    -    Wikipedia
    -
    -For more detailed information on the PageRank algorithm, refer to the Wikipedia article on PageRank.
    +For more detailed information on the PageRank algorithm, refer to the [PageRank article on Wikipedia](https://en.wikipedia.org/wiki/PageRank).

    Copy link

    qodo-merge-pro bot commented Jan 16, 2025

    CI Failure Feedback 🧐

    (Checks updated until commit b264509)

    Action: check-spelling

    Failed stage: Check Spelling [❌]

    Failed test name: spelling_check

    Failure summary:

    The action failed because the spelling check detected spelling errors in the documentation files
    being processed. The check was running through various markdown files (*.md) when it encountered
    spelling mistakes.

    Relevant error logs:
    1:  ##[group]Operating System
    2:  Ubuntu
    ...
    
    561:  > Processing: commands/acl.md
    562:  > Processing: commands/graph.list.md
    563:  > Processing: commands/graph.constraint-drop.md
    564:  > Processing: third-party.md
    565:  > Processing: bolt_support.md
    566:  > Processing: path_algorithm.md
    567:  > Processing: llm_support.md
    568:  > Processing: getting_started.md
    569:  !!!Spelling check failed!!!
    570:  ##[error]Files in repository contain spelling errors
    

    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"
    

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    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.

    1 participant