Novice question: after using usethis::use_github_release(), what do you use to make the source code files (.zip and tar.gz) to attach to the release? devtools::build()? I'm a Mac user so using that function produces a .tgz file for the binary version. Is there any implication of using this format for non-Mac users? From what I understood, devtools::build() does more than simply compressing the project so I presume that right clicking the folder and click "compress" is not recommended.
What's your use case for this?
The source code files are attached "automatically" Managing releases in a repository - GitHub Docs I don't remember doing nothing special beside clicking after I use usethis::use_github_release() 
But do you mean that you want to provide binaries to users? If so you could for instance look into R-universe, you could set up your universe so that it builds releases only. Example: https://github.com/carpentries/carpentries.r-universe.dev/blob/ebb35946fc502273abaa30332b49b9905dc1cb68/packages.json#L9
Thanks, since I saw the "Attach binaries by dropping them here or selecting them" box without any file attached to it, I thought it was my job to make those files. I've just clicked on the publish release button and the files are there 
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
If you have a query related to it or one of the replies, start a new topic and refer back with a link.