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

fix: properly handle --touch when using a storage provider #2705

Merged
merged 2 commits into from Feb 19, 2024

Conversation

johanneskoester
Copy link
Contributor

Description

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

Copy link
Contributor

Please format your code with black: black snakemake tests/*.py.

Copy link

sonarcloud bot commented Feb 19, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@johanneskoester johanneskoester merged commit fca138d into main Feb 19, 2024
35 checks passed
@johanneskoester johanneskoester deleted the fix/storage-touch branch February 19, 2024 12:52
johanneskoester pushed a commit that referenced this pull request Feb 19, 2024
🤖 I have created a release *beep* *boop*
---


##
[8.4.10](v8.4.9...v8.4.10)
(2024-02-19)


### Bug Fixes

* properly handle --touch when using a storage provider
([#2705](#2705))
([fca138d](fca138d))

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

None yet

1 participant