From 82b172e89580ebb2902579913eb63ce5c1a73200 Mon Sep 17 00:00:00 2001 From: Nico Matentzoglu Date: Tue, 12 Nov 2024 20:50:08 +0200 Subject: [PATCH] Reinstating two ODK docs with wrong URLs This is broken in ODK unfortunately, need to wait until next major release! --- docs/odk-workflows/ManageDocumentation.md | 5 ++--- docs/odk-workflows/ReleaseWorkflow.md | 2 +- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/odk-workflows/ManageDocumentation.md b/docs/odk-workflows/ManageDocumentation.md index acf4d6d..419f6b5 100644 --- a/docs/odk-workflows/ManageDocumentation.md +++ b/docs/odk-workflows/ManageDocumentation.md @@ -38,10 +38,9 @@ The documentation is _not_ automatically updated from the Markdown, and needs to If everything was successful, you will see a message similar to this one: ``` - INFO - Your documentation should shortly be available at: https://information-artifact-ontology.github.io/noname/ + INFO - Your documentation should shortly be available at: https://information-artifact-ontology.github.io/ontology-metadata/ ``` -3. Just to double check, you can now navigate to your documentation pages (usually https://information-artifact-ontology.github.io/noname/). +3. Just to double check, you can now navigate to your documentation pages (usually https://information-artifact-ontology.github.io/ontology-metadata/). Just make sure you give GitHub 2-5 minutes to build the pages! - diff --git a/docs/odk-workflows/ReleaseWorkflow.md b/docs/odk-workflows/ReleaseWorkflow.md index 6de746a..2b922b1 100644 --- a/docs/odk-workflows/ReleaseWorkflow.md +++ b/docs/odk-workflows/ReleaseWorkflow.md @@ -44,7 +44,7 @@ Once your [CI checks](ContinuousIntegration.md) have passed, and your reviews ar ## Create a GitHub release -1. Go to your releases page on GitHub by navigating to your repository, and then clicking on releases (usually on the right, for example: https://github.com/information-artifact-ontology/noname/releases). Then click "Draft new release" +1. Go to your releases page on GitHub by navigating to your repository, and then clicking on releases (usually on the right, for example: https://github.com/information-artifact-ontology/ontology-metadata/releases). Then click "Draft new release" 1. As the tag version you **need to choose the date on which your ontologies were build.** You can find this, for example, by looking at the `omo.obo` file and check the `data-version:` property. The date needs to be prefixed with a `v`, so, for example `v2020-02-06`. 1. You can write whatever you want in the release title, but we typically write the date again. The description underneath should contain a concise list of changes or term additions. 1. Click "Publish release". Done.