Skip to content

Commit c2eec95

Browse files
committed
more tweaking
1 parent 436bd77 commit c2eec95

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

{{cookiecutter.project_name}}/.github/next_steps/04_citation.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -35,10 +35,10 @@ The repository has been set up with a [GitHub action](https://github.com/marketp
3535
It is likely that your `CITATION.cff` currently doesn't pass validation. The error messages you get from `cffconvert` are unfortunately a bit cryptic, but doing the following likely helps:
3636

3737
- [ ] Fill in your given name for `given-name`
38-
- [ ] Check if the `family-name` key needs updating. If your last name has a name particle like `von` or `van` or `de`, use the `name-particle` key; if your name has a suffix like `Sr` or `IV`, use name-suffix. For details, refer to the schema description: https://github.com/citation-file-format/citation-file-format
38+
- [ ] Check if the `family-name` key needs updating. If your last name has a name particle like `von` or `van` or `de`, use the `name-particle` key; if your name has a suffix like `Sr` or `IV`, use `name-suffix`. For details, refer to the schema description: https://github.com/citation-file-format/citation-file-format
3939
- [ ] Update the value of the `orcid` key. If you do not have an orcid yet, you can get one here [https://orcid.org/](https://orcid.org/).
40-
- [ ] Update `date-released` using the YYYY-MM-DD format
40+
- [ ] Update `date-released` using the YYYY-MM-DD format.
4141
- [ ] Update the `doi` key with the conceptDOI for your repository (see [https://help.zenodo.org](https://help.zenodo.org/) for more information on what a conceptDOI is). If your project doesn't have a DOI yet, you can use the string `10.0000/FIXME` to pass validation.
42-
- [ ] Update the `keywords` array with some keywords of your own that describe your project
42+
- [ ] Update the `keywords` array with some keywords of your own that describe your project.
4343

4444
Once you do all the steps above, the `cffconvert` workflow will tell you what content it expected to see in `.zenodo.json`. Copy-paste from the GitHub Action log into a new file `.zenodo.json`. Afterwards, the `cffconvert` GitHub Action should be green.

0 commit comments

Comments
 (0)