Originally forked from this repo, the only changes I had made were customizing the the inputs so that it will extract papers on topics that I am interested in.
The instructions are pretty straightforward, as documented, however, I added a quarto site for better usability. Otherwise the results will appear just as fine on digests.md
Repo: https://github.com/nghuixin/tocify
Quarto-rendered site published via Github Pages: https://nghuixin.github.io/tocify/
Customize inputs
Edit feeds.txt to add RSS feeds (Journal Name | URL), interests.md (keywords / narrative seed used for relevance), prompt.txt if you want different ranking/scoring behavior
Deploy Quarto site
In _quarto.yml, let Quarto use its default website output (_site/),
project:
type: website
output-dir: _siteQuarto’s GitHub Pages docs cover the overall approach for rendering/publishing, and this works nicely with the Github Pages artifact deploy model
Add a GitHub Action workflow
Create this file quarto-pages.yml under the folder .github/workflows/
quarto renderbuilds site locally on the runner.upload-pages-artifactpackages_site/for Pages.deploy-pagespublishes that artifact to GitHub Pages.- Quarto provides an official setup action for CI.
name: Publish Quarto site to GitHub Pages
on:
push:
branches: [ main ]
workflow_dispatch:
permissions:
contents: read
pages: write
id-token: write
concurrency:
group: "pages"
cancel-in-progress: true
jobs:
build:
runs-on: ubuntu-latest
steps:
- name: Check out repository
uses: actions/checkout@v4
- name: Set up Quarto
uses: quarto-dev/quarto-actions/setup@v2
run: quarto render
- name: Upload Pages artifact
uses: actions/upload-pages-artifact@v3
with:
path: _site
deploy:
runs-on: ubuntu-latest
needs: build
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
steps:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v4Push changes
git add .github/workflows/quarto-pages.yml _quarto.yml
git commit -m "Deploy Quarto site with GitHub Pages"
git push- Under the Actions tab, the workflow pages build and deployment should run.
- When it completes, GitHub Pages will be live at your repo’s Pages URL (shown in the deploy job output).
- The pages-build-and-deployment workflow will automatically rebuild the site on every push to
mainand during the weekly scheduled commit. It will also rebuild when the Week ToC Digest workflow is run manually