The-Strategy-Unit / The-Strategy-Unit/TPMAs
How best to serve versioned files?
@Lextuga007 is already working on this.
Since Sep 10, 2026.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
What is the best way to version files in this repo and refer to them from other repos?
For example, let's imagine a Shiny app that contains a reference file. The app and the file are in the same repo and therefore they are the same version. If the reference file is moved into this repo, the app and the file versions will become decoupled. Independent changes may happen in the app or to the file, so a new release of the app should be tied to the concurrent version of the reference file.
We serve the json schema from nhp_models with a branch per version. Could something similar be achieved here? There could be a lot of files to serve, so it may not be viable.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.