-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove lookup-refs #303
Open
m7pr
wants to merge
1
commit into
main
Choose a base branch
from
remove_lookups
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Remove lookup-refs #303
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The description file doesn't specify the (dev) version required for teal.modules.clinical, teal or tern. I assume that teal and TMC are still on devel but tern was recently published (2025-01-17) and I'm not totally sure if it needs the devel version or not. Could you add it? This might help users that attempt to use this catalog on older versions of packages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@llrs-roche I am not sure what versions of dependencies should be added in here neither.
tmc and teal are up to be released, so probably we should stick to the dev versions.
tern is published on CRAN but there were already 3 vbumps in the dev version of this package.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then better to make the dependency explicit, that do not state it and hope for the best.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think released versions of all the dependcies could be added.
What are your thoughts @donyunardi @pawelru @shajoezhu @vedhav
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey Marcin. This one is a tricky one - watch out!
First of all - we are running both "all-stable" and "all-devel" installations. It is assumed that this is controlled mostly by R pkg repos: for stable we are using r-universe/ie and for devel we are using r-universe/pharmaverse. My understanding is that if you put something to Remotes it's going to be used in both which is not what we want (or we can skip-remotes in the stable somehow?)
(I putted refs to r-cmd-check pipelines but the same logic exists for pkgdown)
On the other hand - this repo will be archived rather sooner than later and we will move on to have internal catalog so please don't overdo this if you know what I mean.