Skip to content

Add pkgdown workflow for GitHub Pages deployment#155

Merged
soodoku merged 1 commit intomasterfrom
codex/set-up-docs-with-pkgdown-on-github-pages
Sep 22, 2025
Merged

Add pkgdown workflow for GitHub Pages deployment#155
soodoku merged 1 commit intomasterfrom
codex/set-up-docs-with-pkgdown-on-github-pages

Conversation

@soodoku
Copy link
Copy Markdown
Member

@soodoku soodoku commented Sep 22, 2025

Summary

  • add a GitHub Actions workflow that builds the pkgdown site and deploys it to the gh-pages branch
  • align the pkgdown site URL with the gojiplus GitHub Pages hostname

Testing

  • attempted Rscript -e 'pkgdown::build_site()' (fails: Rscript not available in container)

https://chatgpt.com/codex/tasks/task_e_68d0df6c4594832f93bdd8e089fe0444

@soodoku soodoku merged commit 7993cd6 into master Sep 22, 2025
3 checks passed
@soodoku soodoku deleted the codex/set-up-docs-with-pkgdown-on-github-pages branch September 22, 2025 05:35
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Codex Review: Here are some suggestions.

Reply with @codex fix comments to fix any unresolved comments.

About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you open a pull request for review, mark a draft as ready, or comment "@codex review". If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex fix this CI failure" or "@codex address that feedback".

Comment on lines +3 to +5
on:
push:
branches: [ master ]
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[P1] Trigger pkgdown workflow on existing main branch

The new workflow only listens for pushes to master, but this repository’s branches are main and work. Because the master branch does not exist here, documentation changes will never trigger a pkgdown build and the site won’t deploy on pushes. Please change the trigger to the actual default branch so the workflow can run.

Useful? React with 👍 / 👎.

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant