Skip to content

docs: clearly explain report rendering to ZIP archive#3357

Merged
dlaehnemann merged 7 commits intomainfrom
docs/properly-highlight-report-zip-functionality
Mar 10, 2025
Merged

docs: clearly explain report rendering to ZIP archive#3357
dlaehnemann merged 7 commits intomainfrom
docs/properly-highlight-report-zip-functionality

Conversation

@dlaehnemann
Copy link
Copy Markdown
Member

@dlaehnemann dlaehnemann commented Mar 10, 2025

This addresses the first part of #3319, by making the explanations of ZIP archive reports better.

QC

  • The PR contains a test case for the changes or the changes are already covered by an existing test case.
  • The documentation (docs/) is updated to reflect the changes or this is not necessary (e.g. if the change does neither modify the language nor the behavior or functionalities of Snakemake).

Summary by CodeRabbit

  • Documentation
    • Enhanced the report generation guide with clearer instructions for creating self-contained reports in both HTML and ZIP formats.
    • Expanded details on report content, including runtime statistics, provenance information, and workflow topology.
    • Provided additional guidance for custom layouts, annotations, and partial reports.
    • Updated the help text to offer improved clarity on selecting the optimal report format based on dataset size.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 10, 2025

📝 Walkthrough

Walkthrough

This pull request updates the Snakemake documentation and CLI help text for report generation. The documentation now includes additional sections detailing how to include results in reports, produce self-contained HTML and ZIP archive reports, create partial reports, and apply custom layouts. It also clarifies that generated reports contain runtime statistics, provenance information, and workflow topology by default. In the CLI, the help text for the --report argument has been enhanced to clearly explain the differences between HTML and ZIP formats, including guidance on handling various dataset sizes. No code functionality was altered.

Changes

File Change Summary
docs/snakefiles/.../reporting.rst Updated report generation documentation by adding new sections on "Including results in a report", "Self-contained HTML file", "Self-contained ZIP archive", "Partial reports", and "Custom layout". Enhanced descriptions cover annotations, default content, and styling customization.
snakemake/cli.py Revised help text for the --report argument to clarify that the report is self-contained, includes default statistics and provenance information, and advises on selecting HTML for smaller datasets and ZIP for larger datasets with instructions for viewing reports.

📜 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 bb18ce9 and ace54f2.

📒 Files selected for processing (1)
  • docs/snakefiles/reporting.rst (5 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • docs/snakefiles/reporting.rst
⏰ Context from checks skipped due to timeout of 90000ms (40)
  • GitHub Check: testing (10, 3.12, dash)
  • GitHub Check: testing (10, 3.12, bash)
  • GitHub Check: testing (10, 3.11, bash)
  • GitHub Check: testing (9, 3.12, dash)
  • GitHub Check: testing (9, 3.12, bash)
  • GitHub Check: testing (9, 3.11, bash)
  • GitHub Check: testing (8, 3.12, dash)
  • GitHub Check: testing (8, 3.12, bash)
  • GitHub Check: testing (8, 3.11, bash)
  • GitHub Check: testing (7, 3.12, dash)
  • GitHub Check: testing (7, 3.12, bash)
  • GitHub Check: testing (7, 3.11, bash)
  • GitHub Check: testing (6, 3.12, dash)
  • GitHub Check: testing (6, 3.12, bash)
  • GitHub Check: testing (6, 3.11, bash)
  • GitHub Check: testing (5, 3.12, dash)
  • GitHub Check: testing (5, 3.12, bash)
  • GitHub Check: testing (5, 3.11, bash)
  • GitHub Check: testing (4, 3.12, dash)
  • GitHub Check: testing (4, 3.12, bash)
  • GitHub Check: testing (4, 3.11, bash)
  • GitHub Check: testing (3, 3.12, dash)
  • GitHub Check: testing-windows (10)
  • GitHub Check: testing (3, 3.12, bash)
  • GitHub Check: testing-windows (9)
  • GitHub Check: testing (3, 3.11, bash)
  • GitHub Check: testing-windows (8)
  • GitHub Check: testing (2, 3.12, dash)
  • GitHub Check: testing-windows (7)
  • GitHub Check: testing-windows (6)
  • GitHub Check: testing (2, 3.12, bash)
  • GitHub Check: testing-windows (5)
  • GitHub Check: testing (2, 3.11, bash)
  • GitHub Check: testing-windows (4)
  • GitHub Check: testing (1, 3.12, dash)
  • GitHub Check: testing-windows (3)
  • GitHub Check: testing (1, 3.12, bash)
  • GitHub Check: testing-windows (2)
  • GitHub Check: testing (1, 3.11, bash)
  • GitHub Check: testing-windows (1)

🪧 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.
  • @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
Copy Markdown
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: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 359ae2e and d3339df.

📒 Files selected for processing (2)
  • docs/snakefiles/reporting.rst (5 hunks)
  • snakemake/cli.py (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.py`: Do not try to improve formatting. Do not suggest ...

**/*.py: Do not try to improve formatting.
Do not suggest type annotations for functions that are defined inside of functions or methods.
Do not suggest type annotation of the self argument of methods.
Do not suggest type annotation of the cls argument of classmethods.
Do not suggest return type annotation if a function or method does not contain a return statement.

  • snakemake/cli.py
🪛 GitHub Check: Check for spelling errors
docs/snakefiles/reporting.rst

[failure] 10-10:
complext ==> complexity, complex

🪛 GitHub Actions: Codespell
docs/snakefiles/reporting.rst

[error] 10-10: codespell: 'complext' should be corrected to 'complexity, complex'.

⏰ Context from checks skipped due to timeout of 90000ms (40)
  • GitHub Check: testing (10, 3.12, dash)
  • GitHub Check: testing (10, 3.12, bash)
  • GitHub Check: testing (10, 3.11, bash)
  • GitHub Check: testing (9, 3.12, dash)
  • GitHub Check: testing (9, 3.12, bash)
  • GitHub Check: testing (9, 3.11, bash)
  • GitHub Check: testing (8, 3.12, dash)
  • GitHub Check: testing (8, 3.12, bash)
  • GitHub Check: testing (8, 3.11, bash)
  • GitHub Check: testing (7, 3.12, dash)
  • GitHub Check: testing (7, 3.12, bash)
  • GitHub Check: testing (7, 3.11, bash)
  • GitHub Check: testing (6, 3.12, dash)
  • GitHub Check: testing (6, 3.12, bash)
  • GitHub Check: testing (6, 3.11, bash)
  • GitHub Check: testing (5, 3.12, dash)
  • GitHub Check: testing (5, 3.12, bash)
  • GitHub Check: testing (5, 3.11, bash)
  • GitHub Check: testing (4, 3.12, dash)
  • GitHub Check: testing (4, 3.12, bash)
  • GitHub Check: testing (4, 3.11, bash)
  • GitHub Check: testing (3, 3.12, dash)
  • GitHub Check: testing (3, 3.12, bash)
  • GitHub Check: testing-windows (10)
  • GitHub Check: testing (3, 3.11, bash)
  • GitHub Check: testing-windows (9)
  • GitHub Check: testing (2, 3.12, dash)
  • GitHub Check: testing-windows (8)
  • GitHub Check: testing (2, 3.12, bash)
  • GitHub Check: testing-windows (7)
  • GitHub Check: testing (2, 3.11, bash)
  • GitHub Check: testing-windows (6)
  • GitHub Check: testing (1, 3.12, dash)
  • GitHub Check: testing-windows (5)
  • GitHub Check: testing (1, 3.12, bash)
  • GitHub Check: testing-windows (4)
  • GitHub Check: testing (1, 3.11, bash)
  • GitHub Check: testing-windows (3)
  • GitHub Check: testing-windows (2)
  • GitHub Check: testing-windows (1)
🔇 Additional comments (7)
snakemake/cli.py (1)

957-965: Great improvement to the report documentation!

The updated help text for the --report argument is much clearer. It now properly explains:

  1. Reports are self-contained with default statistics and provenance information
  2. How to choose between HTML (.html) vs ZIP (.zip) formats based on dataset size
  3. The folder structure of ZIP archives and how to view them in a browser

This aligns well with the documentation updates in docs/snakefiles/reporting.rst.

docs/snakefiles/reporting.rst (6)

13-17: Well-structured new section heading

The new section "Including results in a report" with appropriate restructured text reference tag improves document organization and navigation.


262-264: Helpful metadata clarification

This addition clearly explains where the metadata for reports comes from, which is valuable for users to understand how Snakemake tracks execution statistics.


265-285: Well-structured new section on HTML reports

This new section with the appropriate reference tag clearly explains:

  1. The default command to create a report
  2. How to customize the report filename
  3. The limitations of HTML reports for larger workflows

The content is clear and the examples are helpful.


286-301: Clear instructions for ZIP archive reports

This section effectively explains:

  1. When to use ZIP archives (for complex reports with many samples)
  2. How to generate a ZIP archive report
  3. How to navigate the archive after unpacking

The instructions align well with the CLI help text updates.


303-316: Useful partial reports section

This new section provides valuable information about creating reports for specific targets, which helps users:

  1. Generate reports for incomplete workflows
  2. Create reports for specific parts of larger workflows
  3. Generate different reports for alternative target rules

Clear and practical explanation.


317-330: Comprehensive custom layout section

This section provides clear instructions for customizing report appearance with:

  1. How to apply a custom stylesheet
  2. What can be customized (logo, colors)
  3. Links to example code and resources

This is a helpful addition for users wanting to personalize their reports.

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Copy link
Copy Markdown
Member

@cmeesters cmeesters left a comment

Choose a reason for hiding this comment

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

Just a few minor suggestions - no need to accept them all.

@sonarqubecloud
Copy link
Copy Markdown

@dlaehnemann dlaehnemann merged commit 948e8fb into main Mar 10, 2025
49 checks passed
@dlaehnemann dlaehnemann deleted the docs/properly-highlight-report-zip-functionality branch March 10, 2025 16:35
johanneskoester pushed a commit that referenced this pull request Mar 11, 2025
🤖 I have created a release *beep* *boop*
---


##
[8.30.0](v8.29.3...v8.30.0)
(2025-03-11)


### Features

* Add extra input size properties
([#2424](#2424))
([359ae2e](359ae2e))
* shell function calls inside of the 'run' directive now use conda,
container, or envmodules specifications
([#2289](#2289))
([0193e34](0193e34))
* xonsh support for script directive
([#3310](#3310))
([d1c369b](d1c369b))


### Bug Fixes

* include unit test templates in `setup.py`
([#3362](#3362))
([b47252c](b47252c))


### Documentation

* clearly explain report rendering to ZIP archive
([#3357](#3357))
([948e8fb](948e8fb))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
kjohnsen pushed a commit to kjohnsen/snakemake that referenced this pull request Dec 15, 2025
This addresses the first part of snakemake#3319, by making the explanations of
ZIP archive reports better.

### QC
<!-- Make sure that you can tick the boxes below. -->

* [x] The PR contains a test case for the changes or the changes are
already covered by an existing test case.
* [x] The documentation (`docs/`) is updated to reflect the changes or
this is not necessary (e.g. if the change does neither modify the
language nor the behavior or functionalities of Snakemake).


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Documentation**
- Enhanced the report generation guide with clearer instructions for
creating self-contained reports in both HTML and ZIP formats.
- Expanded details on report content, including runtime statistics,
provenance information, and workflow topology.
- Provided additional guidance for custom layouts, annotations, and
partial reports.
- Updated the help text to offer improved clarity on selecting the
optimal report format based on dataset size.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: Christian Meesters <cmeesters@users.noreply.github.com>
kjohnsen pushed a commit to kjohnsen/snakemake that referenced this pull request Dec 15, 2025
🤖 I have created a release *beep* *boop*
---


##
[8.30.0](snakemake/snakemake@v8.29.3...v8.30.0)
(2025-03-11)


### Features

* Add extra input size properties
([snakemake#2424](snakemake#2424))
([359ae2e](snakemake@359ae2e))
* shell function calls inside of the 'run' directive now use conda,
container, or envmodules specifications
([snakemake#2289](snakemake#2289))
([0193e34](snakemake@0193e34))
* xonsh support for script directive
([snakemake#3310](snakemake#3310))
([d1c369b](snakemake@d1c369b))


### Bug Fixes

* include unit test templates in `setup.py`
([snakemake#3362](snakemake#3362))
([b47252c](snakemake@b47252c))


### Documentation

* clearly explain report rendering to ZIP archive
([snakemake#3357](snakemake#3357))
([948e8fb](snakemake@948e8fb))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.

2 participants