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 CITATION.cff #306

Merged
merged 3 commits into from
Jun 18, 2023
Merged

Add CITATION.cff #306

merged 3 commits into from
Jun 18, 2023

Conversation

olebole
Copy link
Member

@olebole olebole commented Jun 1, 2023

Copy link

@kevinmatthes kevinmatthes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added some comments on the basic setup. It already looks very good! There are just some small details I would like to ask you to adjust; see my comments below.

Furthermore, there is a GitHub Action to validate a CFF. I would recommend to set up the Action in order to make sure that your CFF is always valid. The job would be the following:

  cffconvert:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
        with:
          persist-credentials: false
      - uses: citation-file-format/[email protected]
        with:
          args: --validate

The workflow takes only 10 seconds to determine a result (valid / invalid) and takes in sum only 30 seconds when also considering the setup overhead. Just add the above job to any already existing GitHub Action workflow which always runs or create a new workflow file.

CITATION.cff Outdated Show resolved Hide resolved
CITATION.cff Outdated Show resolved Hide resolved
CITATION.cff Outdated Show resolved Hide resolved
CITATION.cff Outdated Show resolved Hide resolved
CITATION.cff Outdated Show resolved Hide resolved
@kevinmatthes
Copy link

In addition to the already mentioned GitHub Action, there are also further integrations available in order to maintain and interact with CFFs, such as an Action to automatically update the release date of the software on release or a CLI to cite further works of which you have the CFF data in the references section of your CFF.

If you need help with the CFF or some integrations for it, I can help you.

@olebole olebole force-pushed the citation-cff branch 3 times, most recently from d84b935 to 7cd6a63 Compare June 1, 2023 08:44
CITATION.cff Outdated Show resolved Hide resolved
@olebole olebole force-pushed the citation-cff branch 6 times, most recently from 2e7c036 to 39e9448 Compare June 1, 2023 09:17
@olebole
Copy link
Member Author

olebole commented Jun 1, 2023

@kevinmatthes Thank you for your help! I resolved all issues and now the validation passes.

I moved the CFF validation to an extra workflow and made it run on CITATION.cff changes only, because the file will change very rarely. I think that a further automation is not required, because the file needs an update only with a new version, which happens at most once per year; and then I can update by hand.

@olebole olebole merged commit fc02bd8 into iraf-community:main Jun 18, 2023
@olebole olebole deleted the citation-cff branch June 18, 2023 19:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Question: How to create a .cff with two suggestions?
2 participants