First, there are some important things you should know about the lifecycle of book artifacts and how the single-direction publishing flow works:
You have a tlf/ directory in the main branch as part of the Quarto book source.
The GitHub Pages website publishes from the gh-pages branch. The content of this branch comes from a (temporary) output directory generated by Quarto, say _book/, when the GitHub Actions workflow is ran.
When the GitHub Actions workflow renders the website, tlf/ will be first copied into the output directory (specified in the beginning of _quarto.yml). Then, when all the chapters are rendered, the RTF and PDF artifacts will be overwritten in the output TLF directory, say _book/tlf/, while nothing will be updated in the source directory tlf/.
The GHA workflow will always build RTF and convert them into PDF every time the workflow is ran, into the output directory _book/tlf/. If the file is different from the previous version, they will be committed and updated, then pushed to the gh-pages branch. This makes the website always display the up-to-date version of the rendered artifacts.
Now comes the action item. These RTF and PDF artifacts are up-to-date in the gh-pages branch using the latest version of r2rtf and code, but the main branch artifacts are outdated. Consider updating the artifacts in the main branch, possibly by copying over the ones from the gh-pages branch.
First, there are some important things you should know about the lifecycle of book artifacts and how the single-direction publishing flow works:
tlf/directory in themainbranch as part of the Quarto book source.gh-pagesbranch. The content of this branch comes from a (temporary) output directory generated by Quarto, say_book/, when the GitHub Actions workflow is ran.tlf/will be first copied into the output directory (specified in the beginning of_quarto.yml). Then, when all the chapters are rendered, the RTF and PDF artifacts will be overwritten in the output TLF directory, say_book/tlf/, while nothing will be updated in the source directorytlf/._book/tlf/. If the file is different from the previous version, they will be committed and updated, then pushed to thegh-pagesbranch. This makes the website always display the up-to-date version of the rendered artifacts.Now comes the action item. These RTF and PDF artifacts are up-to-date in the
gh-pagesbranch using the latest version of r2rtf and code, but themainbranch artifacts are outdated. Consider updating the artifacts in themainbranch, possibly by copying over the ones from thegh-pagesbranch.