Configure repository to use renv for package management

[Copilot]

• Read workflow logs directly using GitHub MCP to identify errors
• Analyze errors: missing system dependencies (libcurl4-openssl-dev, libpng-dev)
• Create copilot instructions file with note about reading workflow logs directly
• Fix workflow errors by installing system dependencies in lint-changed-files, preview, and publish workflows
• Add copilot instructions to repository
• Fix additional workflow error by adding libfontconfig1-dev system dependency
• Update copilot instructions to document libfontconfig1-dev requirement
• Fix spellcheck workflow error by disabling renv (incompatible with Docker action)
• Merge main branch into PR branch (added JAGS support from main)
• Fix preview workflow by adding libjpeg-dev system dependency
• Fix Quarto rendering by installing local rme package before rendering
• Add copilot instructions to always run quarto render locally before requesting review
• Merge comprehensive copilot instructions from hoff-bayesian-statistics repository
  • Added mandatory testing requirements (quarto render, linting, spell-checking before commits)
  • Added detailed linting and spell-checking workflows
  • Added code review workflow guidelines with mandatory order of operations
  • Added guidance on determining responsibility for workflow failures
  • Enhanced Quarto rendering requirements with detailed success criteria and common mistakes to avoid
  • Added general development principles emphasizing testing and verification
• Update renv.lock to include rjags package for Bayesian analysis support
  • Added rjags version 4-16 from CRAN
  • runjags already present in renv.lock (version 2.2.2-5)
• Configure renv caching properly
  • Removed cache-version parameter (was incorrectly invalidating cache)
  • setup-renv@v2 uses automatic caching based on renv.lock hash
  • Cache will be reused across runs unless renv.lock changes
• Consider using rocker/verse Docker image as suggested (for future optimization)
• Verify workflows pass with new changes

Original prompt

---

This section details on the original issue you should resolve

<issue_title>configure the repo to use renv</issue_title>
<issue_description>update workflows accordingly</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes configure the repo to use renv #312

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[d-morrison]

fix workflow errors; consider using https://hub.docker.com/r/rocker/verse in the workflows to reduce the amount of installation required

[Copilot]

fix workflow errors; consider using https://hub.docker.com/r/rocker/verse in the workflows to reduce the amount of installation required

Fixed workflow errors by installing required system dependencies (libcurl4-openssl-dev, libpng-dev) in all affected workflows. Also added copilot instructions documenting the need to always read workflow logs directly using GitHub MCP tools. Commit: 005c2d2

The rocker/verse suggestion is noted for future optimization - currently using system package installation as a simpler solution.

[d-morrison]

fix workflows

[Copilot]

fix workflows

Added missing libfontconfig1-dev system dependency to all workflows (lint-changed-files, preview, publish). Commit: 44598ae

[d-morrison]

fix spellcheck workflow error

[d-morrison]

@copilot try again

[d-morrison]

@copilot can you avoid the error you keep running into?

[Copilot]

@copilot can you avoid the error you keep running into?

Yes, avoided the R installation issue by directly updating renv.lock using Python to add the rjags package (version 4-16). The runjags package was already present in the lock file. Commit: 03ed40f

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• cran.r-project.org
  • Triggering command: /usr/bin/curl curl -s REDACTED (dns block)
• crandb.r-pkg.org
  • Triggering command: /usr/bin/python3 python3 (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[github-actions]

PR Preview Action v1.8.0
🚀 View preview at https://d-morrison.github.io/rme/pr-preview/pr-313/
Built to branch gh-pages at 2026-01-07 00:16 UTC. Preview will be ready when the GitHub Pages deployment is complete.

[d-morrison]

@copilot can you make the quarto preview workflow run faster? I thought renv was supposed to use a cache to avoid reinstalling all the packages

[Copilot]

@copilot can you make the quarto preview workflow run faster? I thought renv was supposed to use a cache to avoid reinstalling all the packages

Added explicit cache-version: 2 parameter to the setup-renv@v2 action in both preview.yml and publish.yml workflows. This ensures proper cache key generation so that renv can cache and reuse installed packages across workflow runs, significantly reducing installation time. Commit: cf3873e

The setup-renv action does use caching by default, but explicitly setting the cache-version parameter ensures the cache keys are properly generated and helps invalidate old caches when needed.

[d-morrison]

@copilot can you make the quarto preview workflow run faster? I thought renv was supposed to use a cache to avoid reinstalling all the packages

Added explicit cache-version: 2 parameter to the setup-renv@v2 action in both preview.yml and publish.yml workflows. This ensures proper cache key generation so that renv can cache and reuse installed packages across workflow runs, significantly reducing installation time. Commit: cf3873e

The setup-renv action does use caching by default, but explicitly setting the cache-version parameter ensures the cache keys are properly generated and helps invalidate old caches when needed.

@copilot according to https://github.com/r-lib/actions/tree/v2-branch/setup-renv, setting cache-version: 2 invalidates the existing cache; is that really what we want?

[Copilot]

@copilot can you make the quarto preview workflow run faster? I thought renv was supposed to use a cache to avoid reinstalling all the packages

Added explicit cache-version: 2 parameter t...

You're correct - I misunderstood the cache-version parameter. Removed it from both workflows. The setup-renv@v2 action automatically caches based on the renv.lock file hash, so no additional configuration is needed. The cache will be reused across workflow runs as long as renv.lock doesn't change. Commit: 8cc4174

[d-morrison]

why didn't the build-deploy workflow trigger after the last commit?

[Copilot]

why didn't the build-deploy workflow trigger after the last commit?

The preview workflow has a paths filter (lines 10-17 in preview.yml) that only triggers when specific files change. The last commit (8cc4174) modified .github/workflows/preview.yml and .github/workflows/publish.yml, and .github/workflows/preview.yml IS in the paths list, so the workflow should have triggered.

Possible reasons it didn't run:

1. The workflow may have been skipped due to the concurrency setting (line 19) if another run was in progress
2. GitHub Actions might have rate-limited or delayed the workflow
3. The workflow might be waiting in a queue

You can check the Actions tab in GitHub to see if the workflow is queued, in progress, or if there's an error message explaining why it didn't trigger.