You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a continuation from #200 (comment). I am posting here because I realized "*release" only applies to GitHub.
Would it be possible for the ref parameter to support syntax for the latest Git tag, whether the repo is hosted on GitHub, GitLab, Bitbucket, etc.? This would make it much easier to create tag-based package repositories on R-universe (if I correctly understand @jeroen's advice from r-universe-org/help#378).
The possibility of tags in non-default branches makes the concept of a "latest" tag tricky and even misleading if we are trying to get a release (c.f. r-multiverse/help#26 (comment)). So I no longer think a "latest tag" syntax would add value.
This is a continuation from #200 (comment). I am posting here because I realized "*release" only applies to GitHub.
Would it be possible for the
ref
parameter to support syntax for the latest Git tag, whether the repo is hosted on GitHub, GitLab, Bitbucket, etc.? This would make it much easier to create tag-based package repositories on R-universe (if I correctly understand @jeroen's advice from r-universe-org/help#378).@shikokuchuo, @llrs and I are working on R-releases, a new project that began in the R Consortium Repositories Working Group. We have lofty ambitions to curate Git releases across the entire R package ecosystem in one central R-universe, but we are finding that many maintainers create Git tags without GitHub releases, and that makes things difficult for us.
The text was updated successfully, but these errors were encountered: