docs: update FAQ - recommend ensure function for failing on empty output #2910
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
NelisDrost
changed the title
johanneskoester
approved these changes
Jun 10, 2024
|
Thank you! |
johanneskoester
pushed a commit
that referenced
this pull request
Jun 11, 2024
🤖 I have created a release *beep* *boop* --- ## [8.14.0](v8.13.0...v8.14.0) (2024-06-11) ### Features * add flag to mark files where path should not be modified ([#2888](#2888)) ([d142b46](d142b46)) * support per rule shell exec setting via resources ([#2862](#2862)) ([ab8d2dd](ab8d2dd)) ### Documentation * update FAQ - recommend ensure function for failing on empty output ([#2910](#2910)) ([b035071](b035071)) --- 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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update the FAQ entry 'How do I make my rule fail if an output file is empty?' to point the user to the
ensure(... , non_empty=True)function documentation.Please check that the :ref: link (intended to point to https://snakemake.readthedocs.io/en/stable/snakefiles/rules.html#ensuring-output-file-properties-like-non-emptyness-or-checksum-compliance) is correct - I'm not familiar enough with sphinx to be 100% confident.
QC
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).