merge dev into main

[JanTautorus]

I think all neccesary development is done for now -> should we merge dev into main?

[energyLS]

I think all neccesary development is done for now -> should we merge dev into main?

Thank you @JanTautorus for bringing this up. Indeed, we are ready to bring in all the changes from dev into main. Before we do this, could you please have a look at #50 and merge it. Furthermore, should I review this PR and potentially clean some things if applicable?

[JanTautorus]

@energyLS I'm not sure how worth an indepth diff versus main is, as we treated dev as our core branch for quite a while. If you want to review I would concentrate on the config, readme and core module / snakemake files.

One thing that still has to be implemented is a workflow pulling all input data from zenodo (and configuring that zenodo folder)

[energyLS]

@energyLS I'm not sure how worth an indepth diff versus main is, as we treated dev as our core branch for quite a while. If you want to review I would concentrate on the config, readme and core module / snakemake files.

One thing that still has to be implemented is a workflow pulling all input data from zenodo (and configuring that zenodo folder)

@JanTautorus I have:

• cleaned the config and some notebooks of the dev branch.
• checked: we track the Zenodo data task here: Post-merge cleaning #41
• Created a new release before the merge of dev into main https://github.com/energyLS/shift/releases/tag/v0.1.0

merging now 🚀