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

[pull] master from erlang:master #253

Merged
merged 2 commits into from
Mar 21, 2025
Merged

[pull] master from erlang:master #253

merged 2 commits into from
Mar 21, 2025

Conversation

pull[bot]
Copy link

@pull pull bot commented Mar 21, 2025

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.1)

Can you help keep this open source service alive? 💖 Please sponsor : )

Summary by Sourcery

Renames the 'line_coverage' coverage mode to 'line' in the code module.

jcpetruzza and others added 2 commits March 20, 2025 18:28
It says it expects `line_coverage`, but it should be `line`.
@pull pull bot added the ⤵️ pull label Mar 21, 2025
@pull pull bot merged commit e2f5947 into garazdawi:master Mar 21, 2025
Copy link

sourcery-ai bot commented Mar 21, 2025

Reviewer's Guide by Sourcery

This pull request modifies the code.erl file in the kernel library to rename the 'line_coverage' coverage mode to 'line'. This change aims to improve clarity and consistency in the naming convention for coverage modes.

Updated class diagram for code.erl coverage modes

classDiagram
  class code {
    -coverage_mode()
  }
  code ..> coverage_mode
  coverage_mode : 'none'
  coverage_mode : 'function'
  coverage_mode : 'function_counters'
  coverage_mode : 'line'
  note for coverage_mode "'line_coverage' has been renamed to 'line'"
  coverage_mode : 'line_counters'
Loading

File-Level Changes

Change Details Files
Renamed the 'line_coverage' coverage mode to 'line'. This change affects the type definition for coverage_mode() in the code.erl file.
  • Renamed line_coverage to line in the coverage_mode() type definition.
lib/kernel/src/code.erl

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants