INCATools / ontology-development-kit

Bootstrap an OBO Library ontology
http://incatools.github.io/ontology-development-kit/
BSD 3-Clause "New" or "Revised" License
212 stars 53 forks source link

Issue updating ODK - cdno-odk.yaml doesn't exist #1061

Closed LilyAndres closed 1 month ago

LilyAndres commented 1 month ago

Hi ODK team, I am trying to update ODK following the "Updating ODK" workflow. When I run the command sh run.sh make update_repo sh run.sh make update_repo

It says:

Screen Shot 2024-05-17 at 10 14 03 pm

I feel like maybe I missed one release? But I updated ODK in February... I hope you can help me. Thanks.

anitacaron commented 1 month ago

Hi @LilyAndres, could you double-check if you have a file in src/ontology/cdno-odk.yaml that looks like this one?

LilyAndres commented 1 month ago

I don't have it. Maybe I missed one of the previous releases?

Screen Shot 2024-05-17 at 10 49 27 pm
anitacaron commented 1 month ago

Have you seen this file? How did you set up this repository?

LilyAndres commented 1 month ago

I started my repo in 2021, following ENVO workflows. I don't remember this yaml file...

anitacaron commented 1 month ago

Could you please share the ENVO workflows? It might need some updates.

LilyAndres commented 1 month ago

I am sorry, I can't find it anymore, it was ages ago. I am just having a look at ENVO and FoodOn and I can't see that file either... Not sure where can be found apart from src/ontology or the the top level of the repo.

LilyAndres commented 1 month ago

Maybe is not easy to solve at the moment, I am just having trouble to run my workflow and I thought it could be because of the new ODK release.

anitacaron commented 1 month ago

That's fine. You can create the cdno-odk.yaml with the desired configuration and run update_repo.

anitacaron commented 1 month ago

I am just having trouble to run my workflow

If you want to create another issue, we can discuss your problem there 😄

LilyAndres commented 1 month ago

Thanks a lot @anitacaron, I will create the file and create another issue later, for my other big problem :) I think we can close this issue now.