Skip to content
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

Add .zenodo.json to auto-populate DOI fields upon version releases #2690

Merged
merged 1 commit into from
Jan 17, 2025

Conversation

yantosca
Copy link
Contributor

Name and Institution (Required)

Name: Bob Yantosca
Institution: Harvard + GCST

Describe the update

In this PR we have added a .zenodo.json file, which will auto-populate fields when a DOI is triggered by each GEOS-Chem (science codebase) release.

Expected changes

These are zero-diff updates and can be merged alongside another GEOS-Chem PR.

.zenodo.json
- Added this JSON file, which will auto-populate the various fields
  for auto-generation of DOIs at Zenodo for each version release.

CHANGELOG.md
- Updated accordingly

Signed-off-by: Bob Yantosca <[email protected]>
@yantosca yantosca added no-diff-to-benchmark This update will not change the results of fullchem benchmark simulations category: Bug Fix Fixes a previously-reported bug labels Jan 16, 2025
@yantosca yantosca added this to the 14.5.2 milestone Jan 16, 2025
@yantosca yantosca requested a review from lizziel January 16, 2025 22:21
@yantosca yantosca self-assigned this Jan 16, 2025
@lizziel
Copy link
Contributor

lizziel commented Jan 17, 2025

Thanks for this update! Could you also apply to Cloud-J?

@yantosca yantosca merged commit 255a13d into dev/no-diff-to-benchmark Jan 17, 2025
@yantosca yantosca deleted the bugfix/add-zenodo-json branch January 17, 2025 16:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: Bug Fix Fixes a previously-reported bug no-diff-to-benchmark This update will not change the results of fullchem benchmark simulations
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants