Max Held

share variables across jobs

1

azure has [this](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch)

factor out steps without separate containers (that are not node.js)

5

This is a little unclear to me. If an action (as was the case so far) always runs in its own container, that'd be quite limiting (but also somewhat robust)....

are actions still cached

3

maybe there's enough caching out of the box in the new gh actions

add default CI/CD workflow to github actions

2

has python packages, so would be nice to have this for R packages as well.

run clang-format

1

... on a repo and commit any chances (if any)

which, basically, deletes this package as it is now. With the yml-based GitHub actions there isn't really any need for templating functions anymore. That'd be usethis #41 , or tic...

automatically figure out where static site gens (rmarkdown etc) write to

3

usually `_site`, but could be anything. Would be good to figure this out programmatically, without pestering the user. I just can't think of an elegant way to do this right...

migrate to native caching

3

Would be nice to save knitr caches (`index_cache/`) and other such build artefacts. GitHub might either provide this out of the box at some point, or we might wait for...

would this even be possible? Not sure how to do this right now in azure *or* github actions.