-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Lyuba Zehl
authored
Nov 13, 2023
1 parent
9c6b341
commit 759318c
Showing
1 changed file
with
9 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,8 +1,14 @@ | ||
# openMINDS build pipeline | ||
|
||
[![GitHub][license-shield]][license-url] | ||
[![GitHub contributors][contributors-shield]][contributors-url] | ||
|
||
This branch contains the code for the build pipeline of this repository. The pipeline gathers the schemas from all metadata models (submodules), interprets and supplements with openMINDS vocabulary information. | ||
|
||
## Create a release | ||
To create a release, define the version and its submodules inside the version.json. Run the "update_commits.py" with the attribute "--version X" which then updates the commit information to the current head of the configured submodule branches. Existing commit hashes for this version will be replaced. | ||
To create a release, define the version and its submodules inside the **version.json**. Run the "update_commits.py" with the attribute "--version X" which then updates the commit information to the current head of the configured submodule branches. Existing commit hashes for this version will be replaced. | ||
|
||
### version.json | ||
The version.json defines the submodule versions which are composing an openMINDS release. | ||
|
||
|
||
Versions defined without commit hash are supposed to point to head of the corresponding branch. If no branch is defined, this means that the latest commit on the **semantically highest version branch** is taken into account. | ||
Versions defined without commit hash are supposed to point to head of the corresponding branch. If no branch is defined, this means that the latest commit on the **semantically highest version branch** is taken into account. |