Open jeroen opened 2 years ago
Notes from a convo elsewhere.
Case where one would maintain a registry file, in which one explicitly sets the tag/commit for each package.
File that'd be updated, for instance, by pull requests where there'd be some sort of formal review
Along these lines, I would love to understand all the features and capabilities of packages.json. The “branch” field you mentioned at #363 was new to me, and I am also wondering if I can add non-GitHub/non-GitLab URLs such as https://mc-stan.org/r-packages, or even CRAN itself. All this would help me wrap my head around what is possible for #363.
Sorry, I think I chose the wrong thread for my comment above.
Write technote about how you would set up a repo that checks updates before publishing (like cran).