refactor(ci): drop redundant cranlike/desc installs #73
Loading…
Reference in a new issue
No description provided.
Delete branch "pr/drop-redundant-cranlike-desc"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
bincraft's DESCRIPTION already pulls both forks viaRemotes::So
pak::pak("git::https://codefloe.com/rpkgs/bincraft.git")resolves the forks and installs them transitively. The explicit follow-uppak::pak("pat-s/cranlike@s3")andpak::pak("pat-s/desc@description-from-remote")calls inupdate-package-index-*.yamlare dead weight.Drops the two lines from all 14
update-package-index-*files.process-updates-*.yamlalready only installsbincraft— this brings the two workflows in sync.bincraft's DESCRIPTION declares 'Imports: cranlike' and 'Remotes: pat-s/cranlike@s3, pat-s/desc@description-from-remote', so pak::pak("git::.../bincraft.git") already resolves and installs both forks via Remotes. The explicit follow-up pak::pak() calls in update-package-index-* were redundant.