Dan Foreman-Mackey

That suggests to me that it might a tectonic issue rather than showyourwork, but we'd need to dig some more because there could certainly be other sources of trouble!

Strange! Thanks for the update. I'll take a closer look at this ASAP (not before later this week - sorry!).

I've narrowed it down to identify that the issue comes from this package (`showkeys`) that is automatically included when building with `showyourwork`: https://github.com/showyourwork/showyourwork/blob/02a746eb844ee4fb054cc2cb1e4b1ef37c1bcff4/showyourwork/workflow/resources/styles/build.tex#L11 I'm not exactly sure what the issue...

Sorry about the slow follow up on this, but I figured out where this issue was coming from! (Thanks to @katiebreivik: https://github.com/katiebreivik/cataclysmic-pileup-paper/pull/1) At the top of the MNRAS template `.tex`...

The Zenodo caching features are so brittle and hard to test that adding any features (let alone maintaining existing features) is extremely low priority on my end. The workflow I...

As an update: I've just released an initial draft of this as an external package that the next SYW can depend on: https://github.com/dfm/snakemake-staging cc @katiebreivik, @adrn, @jiayindong

Pinging @MilesCranmer who has been thinking about (and hacking on) this as well.

@mathren — Interesting! The `preprocess.smk` run will generate a file called `.showyourwork/config.json` which should include this info. Then in `build.smk` this file is loaded into the `config` variable: https://github.com/showyourwork/showyourwork/blob/532b1bc66e73bd281d7333c9384c7823ac0515f7/showyourwork/workflow/build.smk#L27 In...

I'm sorry for the delayed response! Unfortunately I'm not too sure what the problem is here, or if you're still running into issues. Please let us know if you found...

The current implementation of SYW is actually extremely tightly integrated with GitHub because of its heavy use of Actions throughout the workflow. There's an existing issue tracking some refactoring of...