Replace Travis CI and AppVeyor with GitHub Actions

[Copilot]

• Delete .travis.yml
• Delete .appveyor.yml
• Add Remotes: field to DESCRIPTION for GitHub-only hard-dependency packages (Rfits, magicaxis, celestial, ProFound)
• Create .github/workflows/R-CMD-check.yaml using r-lib/actions
• Fix CI failure: remove asgr/Highlander and asgr/ProSpect from Remotes: — their transitive deps (cmaeshpc, ProSpectData) are not in any public registry, and since they are only Suggests they don't need to be in Remotes:
• Fix CI failure: set dependencies: '"hard"' in setup-r-dependencies and add knitr/rmarkdown explicitly so vignettes build without pak attempting to install unavailable Suggests packages
• Clean up .Rbuildignore: remove stale .travis.yml and .appveyor.yml entries

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[asgr]

Can you check that this CI GitHub action actually runs successfully

[asgr]

Quite a few packages need to be installed from Github asgr using the R remotes package:

ℹ Creating lockfile '.github/pkg.lock'

✔ Updated metadata database: 7.77 MB in 15 files.

ℹ Creating lockfile '.github/pkg.lock'
ℹ Updating metadata database
✔ Updating metadata database ... done

ℹ Creating lockfile '.github/pkg.lock'
✖ Creating lockfile '.github/pkg.lock' [8.2s]

Error:
! error in pak subprocess
Caused by error:
! Could not solve package dependencies:

• deps::.:
  • Can't install dependency asgr/Highlander (>= 0.1.7)
  • Can't install dependency asgr/ProSpect
• asgr/Highlander: Can't install dependency cmaeshpc
• cmaeshpc: Can't find package called cmaeshpc.
• asgr/ProSpect: Can't install dependency ProSpectData (>= 1.1.0)
• ProSpectData: Can't find package called ProSpectData.
• any::sessioninfo: dependency conflict
• any::rcmdcheck: dependency conflict

---

Backtrace:

1. pak::lockfile_create(c(deps, extra_deps), lockfile = ".github/pkg.lock", …
2. pak:::remote(function(...) { …
3. err$throw(res$error)

---

Subprocess backtrace:

1. base::withCallingHandlers(cli_message = function(msg) { …
2. get("lockfile_create_internal", asNamespace("pak"))(...)
3. prop$stop_for_solution_error()
4. private$plan$stop_for_solve_error()
5. pkgdepends:::pkgplan_stop_for_solve_error(self, private)
6. base::throw(new_error("Could not solve package dependencies:\n", msg, …
7. | base::signalCondition(cond)
8. global (function (e) …
   Execution halted
   Error: Process completed with exit code 1.

[Copilot]

Quite a few packages need to be installed from Github asgr using the R remotes package:

ℹ Creating lockfile '.github/pkg.lock'...

Fixed in e30fa55. The root cause was that asgr/Highlander and asgr/ProSpect were in Remotes:, which forced pak to resolve all their transitive dependencies — cmaeshpc and ProSpectData — which don't exist in any public registry. Since both packages are only Suggests, they don't need to be in Remotes: at all.

Two changes were made:

1. DESCRIPTION: Removed asgr/Highlander and asgr/ProSpect from Remotes: — pak will now skip them gracefully as unavailable optional packages.
2. R-CMD-check.yaml: Set dependencies: '"hard"' on the setup-r-dependencies step (so pak never attempts to install Suggests packages) and explicitly listed knitr and rmarkdown as extra-packages so vignette building still works.

Can you check that this CI GitHub action actually runs successfully

The CI run did trigger and uncovered a pak dependency resolution failure (see the other comment for details). That has been fixed in e30fa55 — the workflow will now re-run on this push.