Skip to content

Commit

Permalink
Fix line breaks syntax errors
Browse files Browse the repository at this point in the history
  • Loading branch information
rays22 committed Jun 27, 2024
1 parent 73d48a0 commit a646d70
Showing 1 changed file with 9 additions and 6 deletions.
15 changes: 9 additions & 6 deletions docs/odk-workflows/ReleaseWorkflow.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,12 +27,15 @@ To actually run the release, you:
2. Start the release pipeline by issuing the command: `sh run.sh make prepare_release_fast`
NOTE: It is recommended that you run the release pipeline uncoupled from refreshing imports. However, in case you do need to refresh all the imports at this time, you can achieve that by issuing the command: `sh run.sh make prepare_release -B`
3. If everything went well, you should see the following output on your machine:
`...`
`Release files are now in ../.. - now you should commit, push and make a release
`on your git hosting site such as GitHub or GitLab`
`make[1]: Leaving directory '/work/src/ontology'`
`Please remember to update your ODK image from time to time: https://oboacademy.github.io/obook/howto/odk-update/.`
This will create all the specified release targets (OBO, OWL, JSON, and the variants, ont-full and ont-base) and copy them into your release directory (the top level of your repo).

`...`

```
Release files are now in ../.. - now you should commit, push and make a release on your git hosting site such as GitHub or GitLab
make[1]: Leaving directory '/work/src/ontology'
Please remember to update your ODK image from time to time: https://oboacademy.github.io/obook/howto/odk-update/.
```
This will create all the specified release targets (OBO, OWL, JSON, and the variants, ont-full and ont-base) and copy them into your release directory (the top level of your repo).

## Review the release

Expand Down

0 comments on commit a646d70

Please sign in to comment.