Skip to content

[portfolio] Repair pkgdown deployment #1

Closed

Description

This issue is managed by the R package portfolio monitor.

Current evidence

  • Gate: pkgdown
  • State: failing
  • Reason: declared pkgdown site is not live and valid
  • Observed default-branch SHA: 68a835c734082cd9e1c987374ed95ca3737632c6
  • Workflow state: completed; conclusion: success; head SHA: 68a835c734082cd9e1c987374ed95ca3737632c6
  • templateflow: failed (https://bbuchsbaum.github.io/templateflow/)

Repair contract

  • Work on a branch and open a pull request; never push directly to the default branch.
  • Preserve R CMD check, meaningful tests, package semantics, and specialized CI gates.
  • Keep the change limited to this failing gate unless a broader fix is demonstrably required.
  • Report the checks run and any remaining external or repository-setting blocker.
  • A local build is not completion: the monitor closes this issue only after hosted evidence is green.

Assigned repair provider: cursor.

Activity

  1. bbuchsbaum-r-package-portfolio commented on Aug 27, 2026

    @bbuchsbaum-r-package-portfolio
    Author

    @cursor investigate and repair this pkgdown gate. Make the smallest coherent change, preserve existing scientific and test gates, run relevant checks, and open a pull request. Do not push to the default branch, do not weaken or skip tests, and leave this issue open until the portfolio monitor verifies the merged default-branch SHA and hosted evidence.

  2. bbuchsbaum commented on Aug 27, 2026

    @bbuchsbaum
    Owner

    @cursor investigate and repair this pkgdown gate described in the issue. Make the smallest coherent change, preserve existing scientific and test gates, run relevant checks, and open a pull request. Do not push to the default branch, do not weaken or skip tests, and leave this issue open until the portfolio monitor verifies the merged default-branch SHA and hosted evidence.

  3. cursor commented on Aug 27, 2026

    @cursor

    Root cause: pkgdown was deploying cleanly to gh-pages, but GitHub Pages was never enabled (has_pages: false), so https://bbuchsbaum.github.io/templateflow/ 404’d.

    Fix in PR #2 (cursor/fix-pkgdown-pages-enable-5a7c):

    • Added pages: write on the pkgdown job
    • Added an Enable GitHub Pages step (same pattern as neuroim2 / bidser) that POSTs the gh-pages source before deploy

    No package/test/gate changes beyond that workflow tweak. CI is running on the PR; I’m subscribed and waiting for those checks to finish. After merge, the push job should enable Pages and make the hosted site live for the portfolio monitor.

    View PR

    Open in Web Open in Cursor 
  4. bbuchsbaum commented on Aug 27, 2026

    @bbuchsbaum
    Owner

    Settings-only repair applied: GitHub Pages is now configured to publish from gh-pages:/. The Pages deployment succeeded and https://bbuchsbaum.github.io/templateflow/ returns HTTP 200. Cursor PR #2 is unnecessary and has been closed unmerged. This managed issue remains open until the portfolio monitor independently refreshes hosted evidence and closes it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions