Skip to content

Stabilize pkgdown workflow by removing GitHub-head Remotes - #44

Draft
ericward-noaa with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-call-workflow-pkgdown
Draft

Stabilize pkgdown workflow by removing GitHub-head Remotes#44
ericward-noaa with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-call-workflow-pkgdown

Conversation

Copilot AI commented Jul 14, 2026

Copy link
Copy Markdown

call-workflow / pkgdown was failing during dependency installation, not site generation. The workflow resolved lozen/testdown from GitHub HEAD via DESCRIPTION Remotes, and upstream API drift in lozen broke the build.

  • Root cause

    • setup-r-dependencies consumed DESCRIPTION remotes and attempted to build ThinkR-open/lozen from source.
    • Current upstream lozen failed to build in CI (add_rstudioconnect_file export mismatch in golem).
  • Change made

    • Removed GitHub remotes for lozen and testdown from DESCRIPTION.
    • Kept both packages in Suggests, so pkgdown/testdown features remain available through standard package resolution.
  • Why this fixes the workflow

    • Stops the pkgdown job from pinning to moving GitHub HEAD state.
    • Restores deterministic dependency resolution for website builds.
-Remotes:
-    github::ThinkR-open/lozen,
-    github::ThinkR-open/testdown

Copilot AI changed the title [WIP] Fix failing GitHub Actions job call-workflow / pkgdown Stabilize pkgdown workflow by removing GitHub-head Remotes Jul 14, 2026
Copilot AI requested a review from ericward-noaa July 14, 2026 00:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants