ProjectPythia / ProjectPythia/cookbook-template

Links that need updating for a new cookbook created from this template

Open
#183 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

infrastructure
Dominant language
Jupyter Notebook
Stars
25
Forks
29
Avg merge
3d 16h
Merged PRs (30d)
2

Description

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.

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.

The two locations that need updating are:

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the documented trigger-replace-links action and inspect README.md, notebooks/how-to-cite.md, CITATION.cff, and _config.yml at the referenced lines. Update the cookbook repository URLs and the two Zenodo repository IDs, while leaving .github/workflows/trigger-replace-links.yaml unchanged. Done means all listed links and badge identifiers refer to the new cookbook repository.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, jupyter-notebook
Domain
documentation, tooling
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.