Package still refers to and contains old workflow

[mdingemanse]

The packagedown pages somehow still contain the old workflow: https://elpaco-escience.github.io/talkr/articles/workflow.html

The new one is also there: https://elpaco-escience.github.io/talkr/articles/workflows.html

The new one should replace the old one everywhere

[bvreede]

Good catch! This happens sometimes; the quick fix is to re-run the website build manually. The workflow that does this has a manual trigger:

Pressing the 'run workflow' button and running it on the main branch will recreate the page and deploy it to GitHub Pages. It takes a few minutes to run and deploy, but should fix this problem if it occurs again. I just did this, and it has updated the page — refresh if it doesn't work!

[mdingemanse]

Actually it's still the case that readme.md refers to https://elpaco-escience.github.io/talkr/articles/workflow.html (singular) which is the old one that doesn't reflect my work in the user-journeys branch. The right URL to the vignette is https://elpaco-escience.github.io/talkr/articles/workflows.html (plural).

I can correct that (just did in main...112-fix-old-workflow-html) but I still wonder why the old one even still exists.

Root cause is my renaming workflow.Rmd to workflows.Rmd but that change was clearly merged to main (workflow.Rmd (singular) doesn't exist anymore). So, I'm confused. Is there some cache I'm not aware of that keeps the old workflow.html alive?

[bvreede]

Very possible. @PabRod do you know this?

I'll check the PR!

[mdingemanse]

Ready to be closed as the PR is merged, but leaving open to solve the issue of an old workflow.html hanging around somewhere

[PabRod]

I'll take a look at this, but let's tag it as low priority for now.