Repository navigation
Link to the source diff on the GitHub CRAN mirror #4
Description
What and why
The R-hub mirror at https://github.com/cran has a repository for every CRAN package (see https://docs.r-hub.io/#cranatgh). Each version goes in as a single commit and is tagged with git tag. GitHub can therefore show the full source diff between any two versions, either through the commit URL (R-hub's example) or through the repo's /compare page.
The compare URL follows a fixed pattern, so diffify could build it for every R comparison:
https://github.com/cran/{pkgname}/compare/{tag1}...{tag2}
For rmarkdown 2.13 against 2.14 that is cran/rmarkdown@2.13...2.14. GitHub documents the syntax here and here.
Colin called it a neat idea in May 2022 and said the team would think about how best to do it. Another user seconded it in April 2023: the raw diff is "super helpful for identifying changes to non-exported functions that might have caused a change".
Where
R package comparison pages on diffify.com. The app code isn't in this repository, which only holds the README.
Done when
- Each R comparison page links to
https://github.com/cran/<pkg>/compare/<old>...<new>for the two versions shown - The link opens the right diff for a sample of packages, including rmarkdown 2.13 to 2.14
Activity
csgillespie commentedon May 16, 2022
That's a really neat idea that never occurred to me - thanks!
We'll have a think about how best to do this, but definitely, something to consider.
remlapmot commentedon May 16, 2022
My pleasure
jamieRowen-mediacom commentedon Apr 6, 2023
I would like to second this suggestion. The diff is super helpful for identifying changes to non-exported functions that might have caused a change. I also didn't know that this was an option until I saw the suggestion on this issue.
[-]Suggestion: Add link to diff on R-hub GitHub CRAN package source code mirror repo[/-][+]Link to the source diff on the GitHub CRAN mirror[/+]