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 piawka to 0.8.2 #51259

Merged
merged 1 commit into from
Oct 8, 2024
Merged

Update piawka to 0.8.2 #51259

merged 1 commit into from
Oct 8, 2024

Conversation

BiocondaBot
Copy link
Collaborator

Update piawka: 0.8.10.8.2

install with bioconda Conda

Info Link or Description
Recipe recipes/piawka (click to view/edit other files)
Summary The powerful AWK script to calculate population statistics in VCF files with support for varying ploidy and missing data
Home https://github.com/novikovalab/piawka
Releases https://github.com/novikovalab/piawka/tags
Recipe Maintainer(s) @taprs
Author @novikovalab

This pull request was automatically generated (see docs).

@BiocondaBot BiocondaBot added autobump Automatic Version Update new version labels Oct 8, 2024
Copy link
Contributor

coderabbitai bot commented Oct 8, 2024

📝 Walkthrough

Walkthrough

This pull request introduces an update to the meta.yaml file for the piawka package. The primary changes include the modification of the version number from 0.8.1 to 0.8.2, reflecting a new release of the package. Additionally, the SHA256 checksum for the source tarball has been updated to align with the new version. All other elements within the meta.yaml file, such as package metadata, source URL, build specifications, requirements, test commands, and descriptive information, remain unchanged. The overall structure of the file is preserved, with the focus solely on updating the version and checksum to ensure accurate representation of the package's latest state.

Possibly related PRs

  • Update piawka #51239: This PR updates the meta.yaml file for the piawka package, changing the version from 0.7.10 to 0.8.1 and updating the SHA256 checksum, which is directly related to the version and checksum updates in the main PR for the same package.

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

🧹 Outside diff range and nitpick comments (1)
recipes/piawka/meta.yaml (1)

23-23: Remove trailing spaces.

There are trailing spaces on lines 23, 35, 36, and 42. While they don't affect functionality, it's good practice to remove them for consistency and cleanliness.

You can remove the trailing spaces from these lines:

  • Line 23 (after tabix)
  • Line 35 (after π, Dxy (or πxy, or Nei's D))
  • Line 36 (after and some more simple stats (Fst, Tajima's D, Ronfort's rho) in VCF files in the command line.)
  • Line 42 (empty line with spaces)

Also applies to: 35-36, 42-42

🧰 Tools
🪛 yamllint

[error] 23-23: trailing spaces

(trailing-spaces)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 3bd4810 and d10d0c4.

📒 Files selected for processing (1)
  • recipes/piawka/meta.yaml (1 hunks)
🧰 Additional context used
🪛 yamllint
recipes/piawka/meta.yaml

[error] 23-23: trailing spaces

(trailing-spaces)


[error] 1-1: syntax error: found character '%' that cannot start any token

(syntax)


[error] 35-35: trailing spaces

(trailing-spaces)


[error] 36-36: trailing spaces

(trailing-spaces)


[error] 42-42: trailing spaces

(trailing-spaces)

🔇 Additional comments (3)
recipes/piawka/meta.yaml (3)

2-2: Version update looks good.

The version has been correctly updated to 0.8.2, which aligns with the PR objective.


1-45: Overall, the changes look good.

The update from version 0.8.1 to 0.8.2 has been correctly implemented in the meta.yaml file. The version number and SHA256 checksum have been updated as expected. The rest of the file remains unchanged, which is appropriate for a minor version update.

A few minor suggestions:

  1. Verify the SHA256 checksum to ensure it matches the new version's tarball.
  2. Remove trailing spaces as mentioned in the previous comment.

Once these small items are addressed, the update should be ready to merge.

🧰 Tools
🪛 yamllint

[error] 23-23: trailing spaces

(trailing-spaces)


[error] 1-1: syntax error: found character '%' that cannot start any token

(syntax)


[error] 35-35: trailing spaces

(trailing-spaces)


[error] 36-36: trailing spaces

(trailing-spaces)


[error] 42-42: trailing spaces

(trailing-spaces)


10-10: Verify the SHA256 checksum.

The SHA256 checksum has been updated for the new version. It's crucial to ensure this checksum is correct for version 0.8.2 of the piawka package.

To verify the checksum, you can run the following script:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autobump Automatic Version Update new version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants