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

feat: allow config files to be processed with YTE #2269

Merged
merged 2 commits into from May 22, 2023

Conversation

johanneskoester
Copy link
Contributor

This is enabled by adding the top-level key

__use_yte__ = true

to the config file.

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

@github-actions
Copy link
Contributor

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

@sonarcloud
Copy link

sonarcloud bot commented May 21, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@johanneskoester johanneskoester merged commit 8e1c22f into main May 22, 2023
8 checks passed
@johanneskoester johanneskoester deleted the feat/config-yte branch May 22, 2023 05:49
johanneskoester pushed a commit that referenced this pull request May 22, 2023
🤖 I have created a release *beep* *boop*
---


##
[7.26.0](v7.25.4...v7.26.0)
(2023-05-22)


### Features

* allow config files to be processed with YTE
([#2269](#2269))
([8e1c22f](8e1c22f))

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