-
Notifications
You must be signed in to change notification settings - Fork 22
feat: use upstream config for contributors #526
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: use upstream config for contributors #526
Conversation
👋 Thanks for opening this PR! The Cookbook will be automatically built with GitHub Actions. To see the status of your deployment, click below. |
@@ -1,7 +1,7 @@ | |||
--- | |||
date: 2025-01-20 | |||
author: Kevin Tyle | |||
tags: ['binderhub', 'maintenance'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gah, please ignore the LSP formatter changes.
@agoose77 our existing CITATION.cff files use the convention
Is that supported here? Or do we have to stick to |
I think the answer is here: https://mystmd.org/guide/frontmatter#frontmatter-authors We can include
and some other fields as well. I'm interested to see if myst can generate an equivalent to our existing CITATION.cff that would comply with Zenodo requirements. If so, we could automate the generation of the .cff file at build time and keep one version of truth for author details across all our many repos. That would be a win. |
I think I meant to put these comments over in ProjectPythia/pythia-config#12, sorry! |
Important
Depends upon ProjectPythia/pythia-config#12
This PR uses GitHub IDs for blog post authors, which are mapped to contributor details in the upstream
pythia.yml
.