Documenting here all the boilerplate link URLs that should be updated from https://github.com/ProjectPythia/cookbook-template/ to the actual home and name of the new cookbook repo.
This should be handled automatically using the trigger-replace-links action as documented in the Cookbook guide, but things go wrong when the specific order of steps outlined in the guide are not followed. In particular, if you run that action before transferring the repo to the ProjectPythia organization, then the links will need manual updated.
Correcting the links to the cookbook repository
What we are really doing is replacing all instances of ProjectPythia/cookbook-template with ProjectPythia/[name of cookbook repo].
If a user has already run the trigger-replace-links action before transferring the repository to the ProjectPythia organization, then we will instead be replacing all instances of [github username]/[name of cookbook repo] with ProjectPythia/[name of cookbook repo].
A search-and-replace in a text editor will take care of this.
Line 5 of README.md -- both the link to the badge icon and the link to the nightly-build.yaml in the same line
Line 46 of CITATION.cff (under the name field, the website field should point to "https://github.com/ProjectPythia/[name of cookbook repo]/graphs/contributors"
The only instance of ProjectPythia/cookbook-template that should be skipped in a search-and-replace is in the workflow file .github/workflows/trigger-replace-links.yaml
Correcting the github.repository_id value in Zenodo links
Our Zenodo badge links for DOIs are keyed the unique values of github.repository_id. All instances of 475509405 (the id value for the template repository) should be replaced with the correct value of github.repository_id for that cookbook.
Our trigger-replace-links action handles this automatically, but again if the steps are taken out of order then these badge links might not be functional.
Documenting here all the boilerplate link URLs that should be updated from
https://github.com/ProjectPythia/cookbook-template/to the actual home and name of the new cookbook repo.This should be handled automatically using the trigger-replace-links action as documented in the Cookbook guide, but things go wrong when the specific order of steps outlined in the guide are not followed. In particular, if you run that action before transferring the repo to the
ProjectPythiaorganization, then the links will need manual updated.Correcting the links to the cookbook repository
What we are really doing is replacing all instances of
ProjectPythia/cookbook-templatewithProjectPythia/[name of cookbook repo].If a user has already run the
trigger-replace-linksaction before transferring the repository to theProjectPythiaorganization, then we will instead be replacing all instances of[github username]/[name of cookbook repo]withProjectPythia/[name of cookbook repo].A search-and-replace in a text editor will take care of this.
README.md-- both the link to the badge icon and the link to thenightly-build.yamlin the same linenotebooks/how-to-cite.mdCITATION.cff(under thenamefield, thewebsitefield should point to"https://github.com/ProjectPythia/[name of cookbook repo]/graphs/contributors"_config.ymlin the fieldrepository_url:The only instance of
ProjectPythia/cookbook-templatethat should be skipped in a search-and-replace is in the workflow file.github/workflows/trigger-replace-links.yamlCorrecting the
github.repository_idvalue in Zenodo linksOur Zenodo badge links for DOIs are keyed the unique values of
github.repository_id. All instances of475509405(the id value for the template repository) should be replaced with the correct value ofgithub.repository_idfor that cookbook.The two locations that need updating are:
README.mdnotebooks/how-to-cite.mdOur
trigger-replace-linksaction handles this automatically, but again if the steps are taken out of order then these badge links might not be functional.